Hi all,
I would just like to share my past experience with Biztalk 2004 and I would like to share it over the internet so that it could help others experiencing this problem with BizTalk 04. The problem we encountered in BizTalk 04 is that we found our message stucked at Active state and that our CPU usage was well 100%. When we tried to look at the Orchestration debugger, we found out that it’s stuck at a shape and to put simply, the orchestration hanged (Just like it was in an infinite loop state). We searched over the internet and found nothing but hot fixes to solve the problem. But luckily for us, we have a logging system that places messages to the database shape after shape so we looked at the database and it showed that our orchestration was not stucked at what the Orchestration debugger had shown us but it was stucked at a later stage of the orchestration (where we had a wrong handling of variables but still is not an infinite loop). So we changed that code and the orchestration ran smoothly. This is just a heads up for people experiencing the same problem because this was a real pain when we debugged this problem and take note that when you run Orch debugger, sometimes (like this instance) it does not show you the real part of the orchestration where your code had left. That’s about it thanks.