- This topic has 4 replies, 1 voice, and was last updated 9 years, 1 month ago by
.
-
Posts
-
-
We have a pretty active Orchestration / Recieve port using the MQSeries adapter. We average around 55,000 messages daily. It seems to handle these messages fine.
However, sporadically about once a day; the polling will stop and the messages will start piling up on the MQSeries Message Queue. I have to manually restart the Host Instance to get the polling to start again.
Anyone experience this or have any advice on where i should start investigating?
Thanks in advance.
-
Very odd behavior. Does it happen the same time every day? Is it predictable? Is the Websphere MQ adapter being disabled? Maybe its a connection issue. I am assuming from the email that there is nothing in the event log when this happens?
-
[quote user="Bryan Corazza"]
Very odd behavior. Does it happen the same time every day? Is it predictable? Is the Websphere MQ adapter being disabled? Maybe its a connection issue. I am assuming from the email that there is nothing in the event log when this happens?[/quote]
It is unpredictable. It has happened twice already today. I might try switching to the new Host Integration Server MQSeries adapter which bypasses the MQAgent and see if that works better. When it happened again, I checked the MQSeries server, BizTalk server and the App Server the orchestration talks to via Web Service, and no events. It just simply stops polling the messages. The Host Instance still is listed as RUNNING. However, as soon as I stop and start it; it works again.
Very frustrating. I dealt with very similar occurance with Queued Components awhile back where the component would stop work w/ MSMQ and the damn components had to be restarted. I never did find a solution for that one. I had to rewrite my own queuing which works solid even today. It seems like I am always dealing with Microsoft related quirks. Hopefully someone will point out something I did wrong, then I will eat my words.
-
-
[quote user="flashbeir"]
Hi,
Did you then find an solution what causes your problem?
[/quote]
No solution; just a culprit. MSDTC for some reason will blow up for no known reason. I had to turn off transactional processing from the MQSeries receive location to make this problem go away. Unfortunately; this removes the guaranteed delivery from the MQSeries queue to BizTalk during the polling process.
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.