I have a orch which is collecting messages published by other orchestration.

All works fine even for 1000 + messages. But for 2500 + messages I see that a lot of messages in Queued Awaiting Processing status. The followingcorrelation receive on the listen shape, starts receiving messages late even though messages are in messagebox.

Then i see 20 to 25 messages getting consumed and then the recieve again starts getting messages after 5 minutes. So there is a delay of 5 mins after every 20 messages or so.

The processing finally completes after a long time but any idea on the issue why the messages are not getting subscribed and staing in this s

Hi ,

You need to scale up your BizTalk Environment as there can be throttled condition when the number of messages goes on increasing .By default any single standalone BizTalk Server specific host instance can open 100 threads at same time .

If your Environment is not sustaining the load then I would suggest to divide the load with creation of multiple host instance and also clustering them as per requirement .

Below MSDN links can help you

General BizTalk Server Optimizations

BizTalk Settings Dashboard, Host Instances Page, .NET CLR Tab

http://blogs.msdn.com/b/biztalkperformance/archive/2007/09/28/threads-db-sessions-and-throttling.aspx

Thanks

Abhishek

Hi,

It looks like that the the orchestration host is throttling due to a high load. In this situation, it will stop processing messages until the ones that are being processing are finished.

Are you uisng the same host for both orchestrations? Maybe using a new one will improve performance.

In addition, you can try adjusting the throttling settings property to improve message and/or orchestration processing for this host.

For more information about throttling: https://msdn.microsoft.com/en-us/library/aa559893.aspx?f=255&MSPPError=-2147217396

Regards.

It's normal that under low load conditions or in a idle status, the BizTalk processes consume low memory.

About throttling, it's not an error, it's a protection mechanism that in your case prevents the BizTalk environment to collapse due to insufficient resources to attend the load.

Regards

It's most probably because the Host Instance is Throttling.

The easiest thing to try is put each operation type, Receive, Orchestration, Send, in separate Hosts/Instances.

Do that, try again and let us know what happened.

You should also monitor these counters so you can report back the exact Throttling state: https://msdn.microsoft.com/en-us/library/aa578302.aspx?f=255&MSPPError=-2147217396

• Proposed as answer by Rachit Sikroria 16 hours 38 minutes ago

Each operation type is already running on separate host instances spread across 6 servers .

However if the host instance is restarted in between all the messages gets processed within seconds. 

I will try throttling counters capture .

They have to be in separate Hosts, not just Instances.  Throttling is as the Host level.

It's most probably because the Host Instance is Throttling.

The easiest thing to try is put each operation type, Receive, Orchestration, Send, in separate Hosts/Instances.

Do that, try again and let us know what happened.

You should also monitor these counters so you can report back the exact Throttling state: https://msdn.microsoft.com/en-us/library/aa578302.aspx?f=255&MSPPError=-2147217396

• Proposed as answer by Rachit Sikroria Wednesday, July 08, 2015 2:25 PM

It's most probably because the Host Instance is Throttling.

The easiest thing to try is put each operation type, Receive, Orchestration, Send, in separate Hosts/Instances.

Do that, try again and let us know what happened.

You should also monitor these counters so you can report back the exact Throttling state: https://msdn.microsoft.com/en-us/library/aa578302.aspx?f=255&MSPPError=-2147217396

• Proposed as answer by Rachit Sikroria Wednesday, July 08, 2015 2:25 PM

It's most probably because the Host Instance is Throttling.

The easiest thing to try is put each operation type, Receive, Orchestration, Send, in separate Hosts/Instances.

Do that, try again and let us know what happened.

You should also monitor these counters so you can report back the exact Throttling state: https://msdn.microsoft.com/en-us/library/aa578302.aspx?f=255&MSPPError=-2147217396

• Proposed as answer by Rachit Sikroria Wednesday, July 08, 2015 2:25 PM

I mean yes they are on separate hosts. We have separate host for rcv snd processing etc.

A restart of host instances makes all in queue msg process in seconds..Any thoughts on that behaviour in relation to throttling ??

There is an event like..The following stored procedure call failed: " { call [dbo].[bts_UpdateMsgbox_xxx

SQL Server returned error string: Transaction (Process ID 310) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction..

And this makes the processing instance start processing messages slow. 

Any one encountered such issue and any possible fix for the same.