Called Orchestrations do not Produce Service Instances in HAT

I’m currently on Microsoft ‘Developing Business Process and Integration Solutions using MS BizTalk Server 2006’ course and in the process of working through a lab, noticed some interesting behaviour when attempting to debug orchestrations that are called from other orchestrations.

It would appear that only asynchronous (aka ‘started’) orchestrations will appear as service instances in HAT and not synchronous (aka ‘called’). I presume this is due to the fact that the called orchestration exists in the thread of the caller, rather than spawning a new thread as in the case of a started orchestration, possibly due to optimisation?

Either way, it would be helpful to receive a service instance in HAT so I can attach and debug…


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s