| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Channel RUNNING and In-Doubt, doesn't recover automatically |
« View previous topic :: View next topic » |
| Author |
Message
|
| gertjb73 |
 Posted: Fri Apr 16, 2010 2:19 am Post subject: Channel RUNNING and In-Doubt, doesn't recover automatically |
 |
|
Newbie
Joined: 30 Mar 2006
Posts: 1
Location: Almere, Netherlands
|
Hi all,
Recently it happend several times that after a remote queuemanager becomes unavailable (e.g. sudden Windows Server reboot), the Sender Channel from Mainframe side (MQ v6) still has channel status RUNNING and gets In-Doubt status YES.
I would expect this channel to get status RETRYING.
After the remote queuemanager is available again, the sender channel is still RUNNING and In-Doubt but no messages are transfered to the remote queuemanager.
After a forced stop of the sender channel with status inactive, the channel stops and becomes running again, this time also sending the messages.
Anybody out there who has encountered the same problem and has a solution for this?
We only encounter this problem om z/OS MQ v6
greetings
Gert Jan |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Fri Apr 16, 2010 3:12 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
we saw the same symptoms in the past, but i think it also was with MQ v5.3.
however, our channels showed "running" while messages where piling up in the xmitq. stop force / start cleared that situation. cause in most cases where network outages or machine failures on the remote end.
the problem seemed to be, that MQ on z/OS did not recognize (or was not told by tcp ip) that the connection was broken, so still thought its fine.
check you are at current maintenance level for tcp ip and mq.
in addition, you could use channel heartbeat in combination with the RCV* CHIN parameters.
we use
RCVTIME=2, RCVTTYPE=MULTIPLY, RCVTMIN=0
which means, that - for a sender - if a hearbeat fails for 2 times the current channel connection is terminated and mq tries to reestablish the connection (channel goes into retry then).
e.g. if your heartbeat on the channel is 30 seconds, and you use the above RCV settings, mq will drop and reconnect latest after 60 seconds when the remote end is gone without telling anybody.
_________________
Regards, Butcher |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
