Hello All,

I am see Channel 'YMT.SV.SRVCON' timed out. below is error log followed by channel snippet.

Thanks

A likely reason for this, as noted in the error message explanation, is a firewall has closed the socket due to inactivity. One way to keep the channel "active" from the perspective of the firewall is to set the heartbeat to a lower value to ensure something flows across the socket more frequently than this time out.

So I advise to change the heartbeat value use to 60 seconds instead of the current (and default) 300 seconds.

Try:

ALTER CHANNEL(YMT.SV.SRVCON) CHLTYPE(SVRCONN) HBINT(60)

Cheers,
Morag

Hello All,

I am see Channel 'YMT.SV.SRVCON' timed out. below is error log followed by channel snippet.

Thanks

Hello Morag,

I changed channel's DISINT  property to 6000(that is default value as per documentation )
HBINT to 300 and qm.ini file's tcp stanza as AtiveAlive =yes.

I don't see any issue anymore. I am not sure about disint property 

thanks 

A likely reason for this, as noted in the error message explanation, is a firewall has closed the socket due to inactivity. One way to keep the channel "active" from the perspective of the firewall is to set the heartbeat to a lower value to ensure something flows across the socket more frequently than this time out.

So I advise to change the heartbeat value use to 60 seconds instead of the current (and default) 300 seconds.

Try:

ALTER CHANNEL(YMT.SV.SRVCON) CHLTYPE(SVRCONN) HBINT(60)

Cheers,
Morag

Hello All,

I am see Channel 'YMT.SV.SRVCON' timed out. below is error log followed by channel snippet.

Thanks

Take care with this DISCINT attribute - the default is NOT 6000 for a SVRCONN type of channel, it is zero. The default 6000 is only for qmgr-qmgr channels, like a SENDER type channel.

Setting DISCINT(6000) for a SVRCONN will end the channel after the client application has been inactive for this period of time. Probably not an issue, but perhaps just make sure that the design of the client application isn't one that sits idle for long periods?

An alternative way of keeping the socket open instead of the way I suggested, is indeed to enable KeepAlive. That is the TCP/IP way of doing heartbeating, and HBINT is the MQ way of doing heartbeating. Both will have the same effect of keeping the socket alive.

Cheers,
Morag

Hello Morag,

I changed channel's DISINT  property to 6000(that is default value as per documentation )
HBINT to 300 and qm.ini file's tcp stanza as AtiveAlive =yes.

I don't see any issue anymore. I am not sure about disint property 

thanks 

A likely reason for this, as noted in the error message explanation, is a firewall has closed the socket due to inactivity. One way to keep the channel "active" from the perspective of the firewall is to set the heartbeat to a lower value to ensure something flows across the socket more frequently than this time out.

So I advise to change the heartbeat value use to 60 seconds instead of the current (and default) 300 seconds.

Try:

ALTER CHANNEL(YMT.SV.SRVCON) CHLTYPE(SVRCONN) HBINT(60)

Cheers,
Morag

Hello All,

I am see Channel 'YMT.SV.SRVCON' timed out. below is error log followed by channel snippet.

Thanks

Hello Morag,

I changed channel's DISINT  property to 6000(that is default value as per documentation )
HBINT to 300 and qm.ini file's tcp stanza as AtiveAlive =yes.

I don't see any issue anymore. I am not sure about disint property 

thanks 

A likely reason for this, as noted in the error message explanation, is a firewall has closed the socket due to inactivity. One way to keep the channel "active" from the perspective of the firewall is to set the heartbeat to a lower value to ensure something flows across the socket more frequently than this time out.

So I advise to change the heartbeat value use to 60 seconds instead of the current (and default) 300 seconds.

Try:

ALTER CHANNEL(YMT.SV.SRVCON) CHLTYPE(SVRCONN) HBINT(60)

Cheers,
Morag

Hello All,

I am see Channel 'YMT.SV.SRVCON' timed out. below is error log followed by channel snippet.

Thanks

I am confused with value 100 min on DISINT as per documentation this is default I altered the value to 100.

When I created the channel the earlier value was 0

during change window I did all change now I am not sure how these combinations worked.

KAINT is auto

please advise.

thanks.

Hello Morag,

I changed channel's DISINT  property to 6000(that is default value as per documentation )
HBINT to 300 and qm.ini file's tcp stanza as AtiveAlive =yes.

I don't see any issue anymore. I am not sure about disint property 

thanks 

A likely reason for this, as noted in the error message explanation, is a firewall has closed the socket due to inactivity. One way to keep the channel "active" from the perspective of the firewall is to set the heartbeat to a lower value to ensure something flows across the socket more frequently than this time out.

So I advise to change the heartbeat value use to 60 seconds instead of the current (and default) 300 seconds.

Try:

ALTER CHANNEL(YMT.SV.SRVCON) CHLTYPE(SVRCONN) HBINT(60)

Cheers,
Morag

Hello All,

I am see Channel 'YMT.SV.SRVCON' timed out. below is error log followed by channel snippet.

Thanks

Perhaps you can provide the link to the page where it says the DISCINT(6000) is the default for SVRCONN channels and we can get that corrected.

The DEFINE channel page for a SENDER and the DEFINE channel page for a SVRCONN show the defaults as 6000 and zero respectively.

The SVRCONN channel was created with DISCINT(0) earlier because that is the default value for that type of channel.

KAINT(AUTO) is fine - that is the only value available on Distributed platforms as keepalive is set to one value for the whole system in TCP/IP.

Cheers,
Morag

I am confused with value 100 min on DISINT as per documentation this is default I altered the value to 100.

When I created the channel the earlier value was 0

during change window I did all change now I am not sure how these combinations worked.

KAINT is auto

please advise.

thanks.

Hello Morag,

I changed channel's DISINT  property to 6000(that is default value as per documentation )
HBINT to 300 and qm.ini file's tcp stanza as AtiveAlive =yes.

I don't see any issue anymore. I am not sure about disint property 

thanks 

A likely reason for this, as noted in the error message explanation, is a firewall has closed the socket due to inactivity. One way to keep the channel "active" from the perspective of the firewall is to set the heartbeat to a lower value to ensure something flows across the socket more frequently than this time out.

So I advise to change the heartbeat value use to 60 seconds instead of the current (and default) 300 seconds.

Try:

ALTER CHANNEL(YMT.SV.SRVCON) CHLTYPE(SVRCONN) HBINT(60)

Cheers,
Morag

Hello All,

I am see Channel 'YMT.SV.SRVCON' timed out. below is error log followed by channel snippet.

Thanks

Please see the link below:

https://www.ibm.com/docs/en/ibm-mq/9.2.x?topic=keywords-discint-disconnect-interval

Perhaps you can provide the link to the page where it says the DISCINT(6000) is the default for SVRCONN channels and we can get that corrected.

The DEFINE channel page for a SENDER and the DEFINE channel page for a SVRCONN show the defaults as 6000 and zero respectively.

The SVRCONN channel was created with DISCINT(0) earlier because that is the default value for that type of channel.

KAINT(AUTO) is fine - that is the only value available on Distributed platforms as keepalive is set to one value for the whole system in TCP/IP.

Cheers,
Morag

I am confused with value 100 min on DISINT as per documentation this is default I altered the value to 100.

When I created the channel the earlier value was 0

during change window I did all change now I am not sure how these combinations worked.

KAINT is auto

please advise.

thanks.

Hello Morag,

I changed channel's DISINT  property to 6000(that is default value as per documentation )
HBINT to 300 and qm.ini file's tcp stanza as AtiveAlive =yes.

I don't see any issue anymore. I am not sure about disint property 

thanks 

A likely reason for this, as noted in the error message explanation, is a firewall has closed the socket due to inactivity. One way to keep the channel "active" from the perspective of the firewall is to set the heartbeat to a lower value to ensure something flows across the socket more frequently than this time out.

So I advise to change the heartbeat value use to 60 seconds instead of the current (and default) 300 seconds.

Try:

ALTER CHANNEL(YMT.SV.SRVCON) CHLTYPE(SVRCONN) HBINT(60)

Cheers,
Morag

Hello All,

I am see Channel 'YMT.SV.SRVCON' timed out. below is error log followed by channel snippet.

Thanks

Thanks - I'll let IBM know the correction that is needed. I suspect what has happened is that page was originally written before the DISCINT field was even applicable to SVRCONN channels, and it didn't get quite enough of an update to explain the different default values when the field was added to SVRCONN channels at later date.

Are you all sorted now? or is there anything else still troubling you?

Cheers,
Morag

Please see the link below:

https://www.ibm.com/docs/en/ibm-mq/9.2.x?topic=keywords-discint-disconnect-interval

Perhaps you can provide the link to the page where it says the DISCINT(6000) is the default for SVRCONN channels and we can get that corrected.

The DEFINE channel page for a SENDER and the DEFINE channel page for a SVRCONN show the defaults as 6000 and zero respectively.

The SVRCONN channel was created with DISCINT(0) earlier because that is the default value for that type of channel.

KAINT(AUTO) is fine - that is the only value available on Distributed platforms as keepalive is set to one value for the whole system in TCP/IP.

Cheers,
Morag

I am confused with value 100 min on DISINT as per documentation this is default I altered the value to 100.

When I created the channel the earlier value was 0

during change window I did all change now I am not sure how these combinations worked.

KAINT is auto

please advise.

thanks.

Hello Morag,

I changed channel's DISINT  property to 6000(that is default value as per documentation )
HBINT to 300 and qm.ini file's tcp stanza as AtiveAlive =yes.

I don't see any issue anymore. I am not sure about disint property 

thanks 

A likely reason for this, as noted in the error message explanation, is a firewall has closed the socket due to inactivity. One way to keep the channel "active" from the perspective of the firewall is to set the heartbeat to a lower value to ensure something flows across the socket more frequently than this time out.

So I advise to change the heartbeat value use to 60 seconds instead of the current (and default) 300 seconds.

Try:

ALTER CHANNEL(YMT.SV.SRVCON) CHLTYPE(SVRCONN) HBINT(60)

Cheers,
Morag

Hello All,

I am see Channel 'YMT.SV.SRVCON' timed out. below is error log followed by channel snippet.

Thanks