Could you add an additional subscriber (that would apply to all messages)
such that you never had a missing subscription?

(i.e. you could have a file send port, and accumulate the messages for
logging purposes, etc. -- or use a no-output-producing adapter, of which
there are a couple samples.)

Depending on what semantics you were looking for, this might be a really bad
idea.  All depends...

Scott Colestock
www.traceofthought.net


"Terry" <Terry@discussions.microsoft.com> wrote in message
news:D06A9228-F902-4425-BC74-A858CD812AEF@microsoft.com...
> Younes,
> Thanks for your responses.
>
> However, sender is not using MSMQT but MSMQ, which is transactional queue,
> which is mandatory setting to communicate with Biztalk's MSMQT, I believe.
> If sender's MSMQ is not getting ACK in return it will try over and over
> again until it reaches some threshold, then it puts the message into
> deadletter queue.
>
> My problem is, until that threshold point, all the subsequent messages
> using
> that queue are being stuck in the outgoing queue, not being delivered to
> the
> Biztalk server. That's why I'm trying to find an answer to cope with this
> situation by deliver that problematic message and get an error message, so
> that subsequent messages being processed.
>
> Any more suggestions?
>
> "Younes Amar" wrote:
> 
>

[ Post a follow-up to this message ]