Home

 

Receive Time Out

 

If you are using TCP as your transport protocol, the receiving end of an idle non-MQI channel connection is also closed if no data is received for a period of time. This period of time is determined according to the HBINT (heartbeat interval) value.

In WebSphere MQ for iSeries, UNIX systems, and Windows systems, the time-out value is set as follows:

1. For an initial number of flows, before any negotiation has taken place, the timeout is twice the HBINT value from the channel definition.

2. When the channels have negotiated a HBINT value, if HBINT is set to less than 60 seconds, the timeout is set to twice this value. If HBINT is set to 60 seconds or more, the timeout value is set to 60 seconds greater than the value of HBINT.

In WebSphere MQ for z/OS, the time-out value is set as follows:

1. For an initial number of flows, before any negotiation has taken place, the timeout is twice the HBINT value from the channel definition.

2. If RCVTIME is set, the timeout is set to one of

   • the negotiated HBINT multiplied by a constant

   • the negotiated HBINT plus a constant number of seconds

   • a constant number of seconds

   depending on the RCVTTYPE parameter, and subject to any limit imposed by RCVTMIN. If you use a constant value of RCVTIME and you use a heartbeat interval, do not specify an RCVTIME less than the heartbeat interval. For details of the RCVTIME, RCVTMIN and RCVTTYPE attributes, see ALTER QMGR in WebSphere MQ Script (MQSC) Command Reference.

 

Parent topic:

Checking that the other end of the channel is still available

ic11310_

 

Home