I stumpled over the following phenomenon that an instance in BizTalk 2013 kept running (in active state) although it did not do anything. You could see in the Webserver logs that the session was not running any longer. When I run the same Webservice with SoapUI, I could see that the Webservice responded with a timeout message (http 500) after 15 minutes:
Application Server Error
500 Connection timed out
Wed Nov 12 16:07:54 2014
BizTalk must have received the same, but somehow did not suspend the message.
Did anyone else run into the same error, or could give me any hint?
