| Author |
Message
|
| fernando28 |
 Posted: Thu Jun 27, 2013 5:49 am Post subject: Cluster sender channel goes to stopped state |
 |
|
Novice
Joined: 07 May 2013
Posts: 20
|
Hi MQ masters!!
Is it possible that some kind of error makes a cluster sender channel in running state turn to stopped? (usually it goes to retrying state...)
I found this at infocenter:
"Errors on channels cause the channel to stop further transmissions. If the channel is a sender or server, it goes to RETRY state because it is possible that the problem may clear itself. If it cannot go to RETRY state, the channel goes to STOPPED state"
I thought that it could never happen....
Thanks in advance. Best regards from Brazil.....Fernando  |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Thu Jun 27, 2013 5:52 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Does the target Qmgr have a DLQ?
Are there any Queue Full conditions on the target Qmgr? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jun 27, 2013 6:39 am Post subject: Re: Cluster sender channel goes to stopped state |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| fernando28 wrote: |
| I thought that it could never happen.... |
Did someone cut the cable? Did someone issue the STOP 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 |
|
|
| mqjeff |
| Posted: Thu Jun 27, 2013 6:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Did the short and long retry intervals expiry?
Did the qmgr at the other side get deleted?
Did someone get-disable the SYSTEM.CLUSTER.TRANSMIT.QUEUE ? |
|
| Back to top |
|
|
| fernando28 |
| Posted: Thu Jun 27, 2013 6:51 am Post subject: |
|
|
Novice
Joined: 07 May 2013
Posts: 20
|
Hi all, thanks for the answers:
There is a DLQ
No queue full conditions
Nobody cut the cable
All support people said they did not stop the channel (But I'm not sure, and all AMQERR0x.LOG already gone) So, who knows??
SCTQ is enabled, target qmgr is available, did not reach long retry interval
I never saw a channel going to STOPPED state without STOP CHANNEL.
But I asked all support people and everybody said they didn't stopped the channel.
So I assume you never saw this happens for some kind of network error, right??
Thanks again...Fernando |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 27, 2013 7:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fernando28 wrote: |
There is a DLQ
...
SCTQ is enabled |
Note that having an enabled SCTQ does not mean the queue manager has a DLQ. Unless the SCTQ (or some other queue) is in the queue manager's attributes then the queue manager has no DLQ.
| fernando28 wrote: |
I never saw a channel going to STOPPED state without STOP CHANNEL.
But I asked all support people and everybody said they didn't stopped the channel. |
The channel will STOP once all the retry intervals have expired.
| fernando28 wrote: |
| So I assume you never saw this happens for some kind of network error, right?? |
If there's a long enough network problem or if the retry is set short then yes I have.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jun 27, 2013 8:16 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If the DLQ can't accept the message (DLQ full, message to big for DLQ, DLQ defined but the QM isn't defined to use it, in MQ 7.5 the channel is set up NOT to use the DLQ, etc) and the channel is dealing with a message it needs to put to the DLQ, then the channel will stop.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fernando28 |
| Posted: Thu Jun 27, 2013 9:37 am Post subject: |
|
|
Novice
Joined: 07 May 2013
Posts: 20
|
Thanks again!!!!
QM is defined to use DLQ and DLQ is empty
Channel attributes are default, so short retry is 10 / 60 and long retry is 999999999 / 1200
This problem happened yesterday, so it was impossible to reach maximum long retry interval
Maybe MSG_TOO_BIG_FOR_Q, but I don't have yesterday error logs.
I think someone stopped the channel, but you know how it works, MQ here has no adm security, so.....
Thanks for all your help......Fernando |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 27, 2013 9:40 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fernando28 wrote: |
| MQ here has no adm security, so..... |
...so people shouldn't be asking you to waste your time looking for a potentially non-existent problem??
It's the old, old story.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Thu Jun 27, 2013 10:28 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Increase your error log size in the qm.ini log by adding:
| Code: |
QMErrorLog:
ErrorLogSize=1048576
|
That is 4X default but might even be too small... This requires a restart of the Qmgr to take effect. |
|
| Back to top |
|
|
| fernando28 |
| Posted: Thu Jun 27, 2013 10:42 am Post subject: |
|
|
Novice
Joined: 07 May 2013
Posts: 20
|
Vitor, you're right. But unfortunatelly we have to do some things to keep our jobs....
Joseph, I will increase error log size.
Thanks guys!!! Best regards from Brazil!!! |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 27, 2013 11:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fernando28 wrote: |
| Vitor, you're right. But unfortunatelly we have to do some things to keep our jobs.... |
This explains where I've been going wrong all these years.... 
But yes, the customer is always right. Even if the customer is barking mad and apparently unable to dress themselves due to the complexities presented by buttons & zips.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fernando28 |
| Posted: Thu Jun 27, 2013 11:21 am Post subject: |
|
|
Novice
Joined: 07 May 2013
Posts: 20
|
| Vitor wrote: |
| fernando28 wrote: |
| Vitor, you're right. But unfortunatelly we have to do some things to keep our jobs.... |
This explains where I've been going wrong all these years....
But yes, the customer is always right. Even if the customer is barking mad and apparently unable to dress themselves due to the complexities presented by buttons & zips. |
 |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jun 27, 2013 1:17 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| fernando28 wrote: |
| QM is defined to use DLQ and DLQ is empty... |
Not the point.
What is the max message length of the DLQ? If a message arrives on a channel, and the message can't be put to the destination queue for any reason whatsoever, AND can't be put on the dead-letter-queue for any reason whatsoever, then the channel will stop. (
| fernando28 wrote: |
| Maybe MSG_TOO_BIG_FOR_Q, but I don't have yesterday error logs... |
The error logs and SYSTEM.CHANNEL.EVENT queue will tell you when the channel stopped, and why - but not about a message being too big.
_________________
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 |
|
|
| JosephGramig |
| Posted: Fri Jun 28, 2013 5:11 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
And bruce2359, this would only be obfuscated by the "too large" msg also having an expiry and reach that expiry and get purged when the channel was manually started. Because otherwise, the channel would not start or stay running and fernando28 would have noticed that (likely).
A interesting string of unfortunate events would have to occur to have this happen and not be somebody failing to fess up that they stopped the channel.
All things being equal, I would bet the human did it. |
|
| Back to top |
|
|
|
|
