| Author |
Message
|
| jim |
 Posted: Sat Apr 05, 2014 12:22 pm Post subject: Cluster sender channel indoubt |
 |
|
Voyager
Joined: 26 Nov 2013
Posts: 94
|
The cluster sender is switching from indoubt yes to no continuously?
nothing found in error logs.  |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Sat Apr 05, 2014 1:44 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
It is perfectly normal for all sender channels to periodically be 'in-doubt' with the remote system as they are moving messages. It is just a stage in the message transfer protocol and nothing to worry about.
What makes you concerned about it ?
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| jim |
| Posted: Sat Apr 05, 2014 8:25 pm Post subject: |
|
|
Voyager
Joined: 26 Nov 2013
Posts: 94
|
| PaulClarke wrote: |
It is perfectly normal for all sender channels to periodically be 'in-doubt' with the remote system as they are moving messages. It is just a stage in the message transfer protocol and nothing to worry about.
What makes you concerned about it ? |
As its is critical application related the alerting is kept high and it generate alert for indoubt.
But when I check the channel switch from indoub "yes or no" and channel is running status.
so I want to confirm the channel is fine or not
 |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Sat Apr 05, 2014 10:31 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
If a channel is still running then the indoubt status is largely irrelevant. It's only when a channel ends that its indoubt status becomes significant. If a channel ends indoubt then it means that messages on its transmission queue may or may not have been delivered meaning, for example, that those message can not be routed to an alternative Queue Manager until the situation has been resolved.
Of course normally even if a channel does end indoubt the situation will resolve itself automatically the next time the channel starts so even then it is nothing to necessarily worry about. After all it's bound to happen from time to time.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| jim |
| Posted: Sun Apr 06, 2014 4:20 am Post subject: |
|
|
Voyager
Joined: 26 Nov 2013
Posts: 94
|
| PaulClarke wrote: |
If a channel is still running then the indoubt status is largely irrelevant. It's only when a channel ends that its indoubt status becomes significant. If a channel ends indoubt then it means that messages on its transmission queue may or may not have been delivered meaning, for example, that those message can not be routed to an alternative Queue Manager until the situation has been resolved.
Of course normally even if a channel does end indoubt the situation will resolve itself automatically the next time the channel starts so even then it is nothing to necessarily worry about. After all it's bound to happen from time to time.
Cheers,
Paul. |
thanks paul
 |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Apr 06, 2014 6:30 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Message Channel Agents (MCAs) want to send (batches of) messages in Units of Work. While the messages are in-transit, the final result of the UofW can not be known (INDOUBT) until both MCAs acknowledge that the messages have been successfully transmitted, and can be committed out of the xmitq, and committed into the destination queue (or DLQ). Until all of this is complete, the channel will be INDOUBT.
If your messages are very large or your channels are very slow, you will likely notice INDOUBT status more than when the channel intermittently sends few small messages across a very fast channel.
Channel INDOUBT is normal and expected behavior.
_________________
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 |
|
|
|
|
