|
Home > Archive > BizTalk Server General > January 2006 > Messages stuck in Outgoing queue due to no consumer is waiting for
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Messages stuck in Outgoing queue due to no consumer is waiting for
|
|
|
| Hi All,
We are sending messages from MSMQ in a server to biztalk server MSMQ/T.
Overall, it's satisfactory.
However, in some situations, one or two messages get stuck in the outgoing
queue because orchestration instance subscribing to that message has trouble
and get terminated.
In this case, biztalk refuses to receive that message and the sending server
keeps trying. As a result and because the transactional queue is forcing the
order, all the other subsequent messages using that message queue will be
blocked, sitting in the outgoing queue waiting to be picked up.
The solution I found so far is recycle the MSMQ service. Then, MSMQ
forcefully send every messages in the outgoing queue and Biztalk server puts
error messages into event log stating, "MSMQT failed to publish the message
coming into the queue DIRECT=OS:[servername]\private$\[queuename], because no
consumer was waiting for it."
The question is,
1. Is there any way that lets biztalk server receive messages even if
there's no subscriber waiting for and generate error message?
2. What is the best practice for this situation?
Any feedbacks will be appreciated.
Thanks,
Terry
| |
| Younes Amar 2005-11-18, 5:52 pm |
| if Hi Terry,
if there is no subscriber, the message will be consumed by adapter, but NOT
be submitted to BizTalk. If there is an inactive subscriber (stopped
Orchestration) , the message will be *routed* to suspended Q and when the
subscriber becomes active (Orch started), the message will be moved from
suspended Q to the BizTalk Q. That s by design.
HTH
Younes
"Terry" <Terry@discussions.microsoft.com> wrote in message
news:80EA83D1-C410-4FDA-9922-4ED318176E5D@microsoft.com...
> Hi All,
>
> We are sending messages from MSMQ in a server to biztalk server MSMQ/T.
> Overall, it's satisfactory.
> However, in some situations, one or two messages get stuck in the outgoing
> queue because orchestration instance subscribing to that message has
> trouble
> and get terminated.
> In this case, biztalk refuses to receive that message and the sending
> server
> keeps trying. As a result and because the transactional queue is forcing
> the
> order, all the other subsequent messages using that message queue will be
> blocked, sitting in the outgoing queue waiting to be picked up.
>
> The solution I found so far is recycle the MSMQ service. Then, MSMQ
> forcefully send every messages in the outgoing queue and Biztalk server
> puts
> error messages into event log stating, "MSMQT failed to publish the
> message
> coming into the queue DIRECT=OS:[servername]\private$\[queuename], because
> no
> consumer was waiting for it."
>
> The question is,
> 1. Is there any way that lets biztalk server receive messages even if
> there's no subscriber waiting for and generate error message?
> 2. What is the best practice for this situation?
>
> Any feedbacks will be appreciated.
>
> Thanks,
>
> Terry
| |
| killbill 2006-01-31, 6:59 pm |
| Hi Terry,
I suppose to answer your question but your question shows that you have done
something where im stuck. I am trying to send msg from MSMQ to Biztalk Server
2006 where MSMQT adapter is listening to receive msg. When i send msg to MSMQ
it stays there and does not reach at Biztalk Server. I am running MSMQ on
WinXP SP2 and Biztalk 2006 on Win2003 SP1.
--
bill
"Terry" wrote:
> Hi All,
>
> We are sending messages from MSMQ in a server to biztalk server MSMQ/T.
> Overall, it's satisfactory.
> However, in some situations, one or two messages get stuck in the outgoing
> queue because orchestration instance subscribing to that message has trouble
> and get terminated.
> In this case, biztalk refuses to receive that message and the sending server
> keeps trying. As a result and because the transactional queue is forcing the
> order, all the other subsequent messages using that message queue will be
> blocked, sitting in the outgoing queue waiting to be picked up.
>
> The solution I found so far is recycle the MSMQ service. Then, MSMQ
> forcefully send every messages in the outgoing queue and Biztalk server puts
> error messages into event log stating, "MSMQT failed to publish the message
> coming into the queue DIRECT=OS:[servername]\private$\[queuename], because no
> consumer was waiting for it."
>
> The question is,
> 1. Is there any way that lets biztalk server receive messages even if
> there's no subscriber waiting for and generate error message?
> 2. What is the best practice for this situation?
>
> Any feedbacks will be appreciated.
>
> Thanks,
>
> Terry
|
|
|
|
|