You use dynamic ports to send messages through the HTTP transport by using multiple instances of the same orchestrations.
During the execution of the Business Process Execution Language for Web Services (BPEL4WS), Microsoft Internet Information Services (IIS) is restarted and some of these messages are sent to the suspended queue.
Events that are similar to the following are generated:
Uncaught exception terminated service
HTTPMultiIn.Service1(2eb5be0d-6a94-374a-ba72-21fb7336bca6), instance
905dc7e4-b8c6-4b01-be28-9e595b476198
Exception from HRESULT: 0xC0C01B13.
Exception type: COMException
Source: Microsoft.BizTalk.Interop.Agent
Target Site: Microsoft.BizTalk.Agent.Interop.IBTMessage
ReadReferencedMessageByID(System.Guid ByRef)
Help Link:
Additional error information:
The BizTalk HTTP receive location "/WSOPortTest01/BTSHTTPReceive.dll" could not
send the HTTP headers to the client.
The BizTalk HTTP receive location "/WSOPortTest01/BTSHTTPReceive.dll" could not
send the BizTalk correlation token to the client.
The "HTTP" adapter is suspending a outbound message going to destination
URL:"HTTP://localhost/WSOPortTest01/BTSHTTPReceive.dll". Details:"The underlying
connection was closed: An unexpected error occurred on a receive.".
The "HTTP" adapter is suspending a outbound message going to destination
URL:"HTTP://localhost/WSOPortTest01/BTSHTTPReceive.dll". Details:"The remote
server returned an error: (503) Server Unavailable.".
The Messaging Engine has suspended "4" message(s) from adapter "HTTP" due to
failures in message processing. Please refer to Health and Activity Tracking tool
for more detailed information on this failure.
Even though IIS is running again, the messages cannot be resumed by using Microsoft BizTalk Server 2004 Health and Activity Tracking (HAT).