Re: Biztalk hang in production environment

Home Page Forums BizTalk 2004 – BizTalk 2010 Biztalk hang in production environment Re: Biztalk hang in production environment

#23218

Sorry for bringing up this old topic, but while searching the web this page was the only one that describes almost the exact problem I’m having. I’m hoping Per found a solution and still reads this forum, or maybe someone else can help me.

A small difference between Per’s environment and ours is that we have BizTalk 2006 R2 Enterprise Edition (v3.6.1404.0). Our system is a physical Dell system, running Windows Server 2003 Standard Edition SP 1 (v5.2) with an Intel Xeon 2.8 GHz cpu and 2 GB RAM.

Just like described above, our system is running fine most of the time. A dozen of different document types are being processed very fast and if anything wrong happens, we get a nice alert (if we programmed it to do so).

We have experienced that BizTalk may stop working properly without warning. We process a lot of files every day and most of them require quick processing. Some people try again if they don’t receive an answer within a minute, so another file is submitted to BizTalk. Meanwhile BizTalk isn’t doing anything with those files, so they just keep adding up to its queue until it decides to continue working. Often some files are processed incorrectly because other services can’t handle all the requests they receive from BizTalk. If someone notices something’s wrong, we can manually correct everything, but the later that happens, the more there is to fix.

The above happened yesterday for – I think – the third time this year. And the fourth time this morning. And the fifth time this afternoon. We decided to do a full reboot and everything seems okay for now. You can understand that I’m a bit concerned however, maybe even scared.

Unlike Per however, we don’t get any errors in our event log that I can relate to these problems. Also, I don’t believe the mentioned error has anything to do with what we describe.

The worst thing about this is that I don’t know what’s causing this. Like I said the problem on this page is the only one I found on the web that is [pretty much] the same as ours.

Hopefully anyone can help me out here. Thanks in advance.