| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| What status the channels are in, when they go in-doubt |
« View previous topic :: View next topic » |
| Author |
Message
|
| rsinha |
 Posted: Thu Mar 04, 2004 5:08 pm Post subject: What status the channels are in, when they go in-doubt |
 |
|
Apprentice
Joined: 29 Aug 2003
Posts: 42
|
Does anyone know, what status the channels have, when they go indoubt permanently, meaning, they don't for whatever reasons, don't get an ack from the receive side?
I'm wondering if I need to monitor channel in-doubt. As I've found on this forum, that send channels will go in-doubt every time there is a batch to send, but soon become not in-doubt after receiving the ack.
So I can't simply put monitorying on in-doubt alone. What other channles status parameter could tell me, if there is something wrong, i.e. channle is in doubt for good and needs manual intervention?
Thanx |
|
| Back to top |
|
 |
| kman |
| Posted: Mon Mar 08, 2004 12:32 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
| check out the Intercommunication Guide and System Administration from the documentation link above. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Tue Mar 09, 2004 4:32 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
A channel will go into INDOUBT usually in one of two instances. The most common is that the Sending channel will lose the ability to connect with it's remote receiving channel whether it is network relate or someone ran a stop chl agains the remote receiver or the remote MQManager becomes unavailable, the receiving channel is not properly defined etc etc. In this case you may see a status of RETRY if you happen to run a dis chstatus against the channel at the moment it reaches its retry interval.
The other reason a channel will go indoubt is if persistance is set and there is a discrepancy between the CURSEQNO of the the sending channel and it's remote receiving channel.
In this instance you need to do a reset chl on the sending channel to match the receiving chl or just reset it to 0.
Another status you may want to monitor is STOPPED
The only other status that I can think of is a "No status found" on a channel that has a DISCINT set to 0 but I am not sure how that would happen.
Regards,
Chris
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Mar 09, 2004 6:16 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If the channel is in doubt, that means the two sides can't automatically determine the state of the last batch of messages sent. You need to compare the LUWIDs at both ends of the channel.
If the LUWIDs are the same, that means the RCVR has committed the in doubt messages on the destination queue(s). You must remove the messages from the XMIT queue, by resolving the SNDR channel and committing the messages.
If the LUWIDs are different, that means the RCVR has not committed the last batch, and the messages on the XMIT queue are important. Resolve the channel with the backout paramter. This places the messages back on the XMITQ, where they can be resent once the channel is up.
Not doing this means you might lose messages, or you might duplicate messages.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
