Hi Terry,
i guess now i understand your problem,

Did you require In-Order delivery? Unfortunately MSMQT always insists on
In-Order delivery (i.e. it's not configurable) which means there can only be
one thread per queue to process messages, multiple threads would cause
interleaving of messages and therefore violate in-order.  This is
potentially a cause of your problem.



You can workaround this with MSMQT by "spraying" messages across multiple
MSMQT queues, or the more preferable approach in most cases is to use MSMQC
which doesn't implement in-order delivery and can therefore use multiple
threads to process incoming messages.



Thx

Younes


"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 ]