Hello,

During peak BizTalk processing, we are getting timeouts in send port (EDI Assembler) for one particular transaction.

The below error is logged in event viewer:
There was a failure executing the send pipeline: "SndToMQ, MQId.SndToMQ, Version=1.0.0.0, Culture=neutral, PublicKeyToken=zwd125c5569r1c0q" Source: "EDI Assembler" Send Port: "MQ.RP" URI: "mqsc://CL.QM/tcp/x.x.x.x(x)/QM/EDI" Reason: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

Please note this send port is for realtime response - so the size is not an issue - the output EDI is only few bytes. Also, the number of parallel requests is also not high. This runs fine all day without any issues. Only during peak load in BizTalk - when other transactions are in process - this send port is impacted.

We used to get a lot of these errors and then we changed the send port priority to 1. The send port priority change reduced the number of errors, but they are still occurring nevertheless.

This Send port is also running under a host instance in a BizTalk server that doesn't process other transactions (same msgbox - but different BizTalk servers).

Looking at the error, seems the message is already picked from Msgbox, but during EDI Assembler, there is a timeout error.

Any thoughts would be appreciated.

Thanks!

• Edited by NathanSPG Wednesday, July 16, 2014 3:34 PM

Hi Nathan,

We are facing the exact same issue. Were you able to figure out the reason for this?

Thanks

What's the load on the SQL Server look like?  The only reasonable source of this error is db access code for Trading Partner Management.

SQL server is pretty stable. Its only during peak BizTalk processing we get this error on the send port. The event log (Both on SQL and BizTalk) does not have any information apart from this error. 

Hi Nathan,

This is surely a case of thread starvation of specific host instance during peak hours . I would suggest to create a new host instance and specific handler for your send port and the the application configuration with newly created adapter handler .

Once done you can check the the environment .

Thanks

Abhishek

Hi Abhishek

Have already tried that. It does reduce the number of errors but does not completely eliminate it.

Thanks