- This topic has 2 replies, 1 voice, and was last updated 9 years, 1 month ago by
.
-
Posts
-
-
-
Have you taken a look and see if perhaps you’re running out of threads in the thread pool? This can be quite common if you have lots of receive locations and send ports (I don’t know how the MQSeries adapter behaves, but the MSMQ adapters are notoriously hungry for threads).
Here are some tips on how to control BizTalk’s threadpool:
http://blogs.msdn.com/kevinsmi/archive/2005/05/04/414749.aspx
http://www.traceofthought.net/PermaLink,guid,273a4374-40fc-4fe4-bbe6-833aa3c84022.aspx-
We have BizTalk 2004 with the MQSeries Adapter. We place messages on a queue and the Orchestration picks them up, processes them and places them on another queue.
Most of the time, messages are placed on the queue, the orchestration reads them, maps them from one schema to another and places the new message in another queue.
Several times a day, the message will be placed in the input queue and sit
there without the orchestration picking it up. I chech the BizTalk Admin
console and the BizTalkServerApplication is still in a running state but
nothing happens.HAT shows no message have been detected and no orchestrations started. Event Viewer shows no errors. I get no detectabale evidence that anything is wrong except the message sits on the input queue.
If I stop then start the BizTalkServerApplication, the message is picked up
and processed. For a while things will continue to work and process message when they arrive until the next time.The input message is of a single schema generated by the same Java code for each message sent. The schema is simple and contains no complexities that could result in different results with respect to the message itself. Since it is not being processed, it is easy to examine and no differences in the message can be found.
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.