| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ Channel won't automatically go to Running from Retrying |
« View previous topic :: View next topic » |
| Author |
Message
|
| bruce2359 |
 Posted: Thu Aug 23, 2018 4:46 am Post subject: Re: MQ Channel won't automatically go to Running from Retryi |
 |
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
These channel attributes control MQs built-in channel RETRY intervals (how often to RETRY, and how many times to RETRY). If your channel(s) are unreliable, then you should RETRY more times in a shorter interval.
| krypton wrote: |
...
LONGRTY(999999999)
LONGTMR(1200)
SHORTRTY(10)
SHORTTMR(60) |
Read about these here https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.5.0/com.ibm.mq.ref.con.doc/q081660_.htm
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Aug 23, 2018 4:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| krypton wrote: |
| Doesn't the above parameter makes the channel change automatically from retrying to running state as soon as the network issue is over? |
It does.
The point I'm making is that the channel doesn't know the network issue is over. After the period of time specified in the parameter the channel MCA will make another attempt to connect to it's partner. It will do this by attempting to restart a conversation over the network. If it's able to do that, the status will change to running. If it's unable to do so it will stay in retry. And the MCA will make another attempt when the period of time in the parameter expires.
The situation that I'm trying to outline is that, irrespective of the status of the network, the MCA is being told by the local IP stack that it's attempt was unsuccessful. All the MCA can do is keep trying, and as long as it's being told it can't it will keep trying. Hence the status of "retrying".
Once the MCA is manually stopped, it's conversation and cached information are discarded by the local network adapter. When it's restarted, it tries to start a conversation, the adapter looks up the details over the working network and you're away.
There's no way of MQ to determine that the network is in fact working when the network component it's talking to is telling it that it isn't every time it asks. The solution to your problem, as I tried to outline above, is that when network connectivity is restored, part of the resolution is to notify all the affected network components that this has occurred.
You can't do that from anywhere other than the network, and certainly not from a network consuming application.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Aug 23, 2018 5:07 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
If all attempts to RETRY the channel fail, then channel will go into STOPPED state. STOPPED state requires manual intervention with a START CHANNEL command.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Aug 23, 2018 5:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| If all attempts to RETRY the channel fail, then channel will go into STOPPED state. STOPPED state requires manual intervention with a START CHANNEL command. |
But in the OP's configuration, retirement will come before the channel stops.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Aug 23, 2018 4:07 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Vitor wrote: |
| bruce2359 wrote: |
| If all attempts to RETRY the channel fail, then channel will go into STOPPED state. STOPPED state requires manual intervention with a START CHANNEL command. |
But in the OP's configuration, retirement will come before the channel stops. |
I once looked at an old development qmgr and noticed a channel had been retrying every 20 minutes for the last 2 years.....
If the channel is critical, review the default settings for the 4 retry attributes and change accordingly. eg. It could do 100 X short retry every 60 secs, followed by 99999999 X long retry every 300 secs. YMMV.
_________________
Glenn |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Aug 24, 2018 4:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gbaddeley wrote: |
| If the channel is critical, review the default settings for the 4 retry attributes and change accordingly. eg. It could do 100 X short retry every 60 secs, followed by 99999999 X long retry every 300 secs. YMMV. |
This allows you to get a minor incident when the monitoring software notices the retrying status and a full on, red alert, danger-danger-will-robinson when it stops.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
