RE: Receive Timeout error

I will try this scenario on a test system by end of this week and get back
to you.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
© 2004 Microsoft Corporation. All rights reserved.
"Please do not send email directly to this alias. This is our online
account name for newsgroup participation only."
>>NNTP-Posting-Date: Fri, 13 May 2021 11:28:01 -0500
>>Subject: Receive Timeout error
>>From: tdonlan@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (tdonlan)
>>Newsgroups: microsoft.public.biztalk.general
>>Mime-Version: 1.0
>>Content-Type: text/plain; charset=ISO-8859-15
>>Content-Transfer-Encoding: 8bit
>>User-Agent: newsSync (BizTalk Server) 16091
>>Message-ID: <7LCdnZOMSs4PSBnfRVn_vg@xxxxxxxxxxxx>
>>Date: Fri, 13 May 2021 11:28:02 -0500
>>Lines: 1
>>X-Complaints-To: abuse@xxxxxxxxxxxx
>>X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
>>X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your
complaint properly
>>X-Postfilter: 1.3.32
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.biztalk.general:13843
>>X-Tomcat-NG: microsoft.public.biztalk.general
>>I have a MLLP Receive (request response) port accepting messages from
>>an outside interface. When the Receive timeout is set to the default
>>(60000), the other interface is getting log messages every 60 seconds
>>like the following:
>>> 05/13/2005 09:03:54
>>> [pdl :PDL :ERR /0:poseidon_out_s] read returned error 0 (No error)
>>> 05/13/2005 09:03:54
>>> [pdl :PDL :ERR /0:poseidon_out_s] PDL signaled exception: code 1,
>>msg device error (remote side probably shut down)
>>> Engine idle -- 05/13/2005 09:04:10
>>This is consistent with what BizTalk documentation states for the
>>Receive Timeout:
>>> On an MLLP receive port, the MLLP Transport Receive Timeout property
>>closes an inactive socket after a specific amount of time based on its
>>value. If no activity is detected on the socket during this time-out
>>value, the receive MLLP socket will close. This occurs to free up
>>resources and to free a BizTalk thread. The port continues to listen
>>for connections and will reopen the port when a new connection is
>>When I set the Receive timeout property to 0 (no timeout), messages
>>are not processed correctly and I get BAM Event Bus errors:
>>> Unhandled exception caught, exception details:
>>System.NullReferenceException: Object reference not set to an
>>instance of an object.
>>> at
>>sender, SendCompletionEventArgs status)
>>> at
>>state, Boolean timeout).
>>I believe the BAM event bus event fails when trying to copy the
>>message over to the tracking database.
>>Is there a way to not have my Receive Port timeout when the property
>>is set to 0?


Relevant Pages