Share this

Secret of MSMQ adapter in BizTalk

For one of our customer we ran into this unique issue in DR environment during DR drill preparation. The traces for one of the EAI application shows the delay of more than 10 seconds in BizTalk and the same application is working fine in other environments (UAT & PROD). After further investigation we found the delay was from the time message gets into MSMQ to the time it is picked up by MSMQ adapter inside BizTalk. We also tested the MSMQ independently for send/receive and it did not take much time. Finally after doing some research work we came to know about of this secret of MSMQ adapter. The MSMQ adapter is designed in such a way that it will either wait for the batch size of 20 messages or wait for 10 seconds before it timeouts and process the incoming messages, whichever occurs first. In our case the batch size of the MSMQ adapter for the application was 20 in DR environment and it is 1 in LIVE.  And we were testing the application only with a single message instead of a batch of 20 messages. Therefore, we see the 10 sec delay every time when the number of message is less than 20. When we changed the batch size to 1 then the delay of 10 sec was resolved. Resource: http://blogs.msdn.com/b/biztalknotes/archive/2013/10/02/delay-while-picking-message-using-msmq-adapter-in-biztalk-server-2010.aspx

Loved this? Spread the word


Gautam

Follow me here

About the Author

My name is Gyanendra Kumar Gautam. I am Solution Consultant, who basically works to hook the stuff together using Microsoft technologies like Azure PaaS, Azure Serverless Services, Microsoft BizTalk Server, and Azure DevOps Services.

You may also like

The source was not found, but some or all event logs could not be searched. To create the source, you need permission to read all event logs to make sure that the new source name is unique. Inaccessible logs: Security.

Yesterday this error came for one of the deployment on production. But the same deployment was working fine on staging environment. A message received by adapter “MSMQ” on receive location “RL_XYZ_RES_09” with URI “FORMATNAME:DIRECT=OS:.\PRIVATE$\XYZ_RES_09” is suspended. Error details: There was a failure executing the receive pipeline: “BTSHttpDecoder.DecoderPipeline, BTSHttpDecoder, Version=1.0.0.0, Culture=neutral, PublicKeyToken=5793a821957af7d1” Source: “MessageDecoderPipelineComponent_F09” Receive Port:

Read More

BizTalk Project Template is missing in Visual Studio 2012

I ran couple of times into this issue so thought of documenting it here. So first of all development of BizTalk Server 2013 application is only supported on Visual Studio 2012. In short, to get BizTalk Project Template do the following steps: Install Visual Studio 2012 Install SQLServer2012 or SQLServer2008R2 SP1 Install BizTalk Server 2013  – Select (mark

Read More

There is no value associated with the property ‘BTS.MessageID’ in the message.

In the following orchestration (This is the HelloWorld sample application at C:\Program Files (x86)\Microsoft BizTalk Server 2013\SDK\Samples\Orchestrations\HelloWorld\)     Inside the message assignment shape I have added the following code. System.Diagnostics.EventLog.WriteEntry(“HelloWorld”,InvoiceMessage(BTS.MessageID)); Now when I deploy and test the HelloWorld application, I get the following error xlang/s engine event log entry: Uncaught exception (see the ‘inner exception’ below)

Read More

Never miss a good story!

 Subscribe to my blog to keep up with the latest news!