| Author |
Message
|
| jeevan |
 Posted: Fri Dec 18, 2009 5:18 pm Post subject: A huge # of messages stuck in SCTQ in FR |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
We saw ( by accident while checking other stuff) that, there are about 12k message stuck in our SCTQ at both of our FR. When we cheked these messages, we can identify that these are for different PR. When we checked the PR, the channel are inactive and when we refresh teh cluster and the channel started, these messages are consumed.
I understand that like other channels, cluster RCVR and SDR channel also go inactive when DSCINT finishes. But once there is messages in the SCTQ at FR going to PR, would not this start the RCVR channel of the PR the message is goinig to?
The only thing I am wondering is that this is MQ 7.0.0.0 whether there is any bug.
Your help will be appreciated. |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Sat Dec 19, 2009 1:59 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
were these cluster channels inactive or retrying?
just like normal channels cluster channels can also go into retrying and get 'stuck' between the short retry timers timing out and long retry timers too far away in time.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jeevan |
| Posted: Sat Dec 19, 2009 3:47 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| Michael Dag wrote: |
were these cluster channels inactive or retrying?
just like normal channels cluster channels can also go into retrying and get 'stuck' between the short retry timers timing out and long retry timers too far away in time. |
They were inactive. But my question is would not they be started when there is message in the SCTQ? |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Sat Dec 19, 2009 4:29 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
if they are inactive then they should be restarted, the point I was trying to make is if they were in retrying mode than what you see makes sense.
you can look at the 7.0.0.1 fix list to see if your problem is in it if you are indoubt or report it to IBM, but they will probably ask you to upgrade to the latest fixlevel anyway...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jeevan |
| Posted: Sat Dec 19, 2009 4:46 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| Michael Dag wrote: |
if they are inactive then they should be restarted, the point I was trying to make is if they were in retrying mode than what you see makes sense.
you can look at the 7.0.0.1 fix list to see if your problem is in it if you are indoubt or report it to IBM, but they will probably ask you to upgrade to the latest fixlevel anyway... |
Thanks a lot. I am contacting IBM and also we are planning to upgrade. I just post here in case some one has had this problem.
I am repeating again, when we refresh cluster, the cluster channel came up and these message to that particular store were consumed. So, we kind of know what is not working, we are just trying to see whether we can find the solutioin ourselves. It couold be we have to upgrade ( we will anyway), or anything else. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Dec 19, 2009 6:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jeevan wrote: |
| Thanks a lot. I am contacting IBM and also we are planning to upgrade. I just post here in case some one has had this problem. |
And we thank you. Do please post any solution or information you come across. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zonko |
| Posted: Sun Dec 20, 2009 10:37 pm Post subject: |
|
|
Voyager
Joined: 04 Nov 2009
Posts: 78
|
REFRESH CLUSTER was the wrong response; indeed it is rarely if ever the right response.
All you needed to do was start the channels.
Cluster channels should indeed be running if there are msgs on the cluster xmitq for the channel. Reasons that the channel might not be running is if it is RETRYING, or if it has been stopped by user action to STOPPED or INACTIVE status.
The recommended software level at WMQv7 is 7.0.1.0. |
|
| Back to top |
|
|
| jeevan |
| Posted: Sun Dec 20, 2009 11:14 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| zonko wrote: |
if it has been stopped by user action to STOPPED or INACTIVE status.
|
The channel was not in STOPPED state but it was in INACTIVE state. And the INACTIVE state was achieved not due to manual effort, but automatically after the DISCINT lapses.
| zonko wrote: |
All you needed to do was start the channels.
|
My question is, if a channel is in INACTIVE state due DISCINT lapses, should not it be restarted automatiaclly when there is msgs in SCTQ? .
Probably, we should not have done REFRESH CLUSGTER but simply start the channel, we just thought to do to test and it worked. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Dec 21, 2009 5:40 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If the channels to QMx were Inactive
AND
There were messages to QMx in the S.C.T.Q.
AND
You have provided all the releveant info
AND
There are no other errors messages
then it smells like a bug to me.
| Quote: |
| The only thing I am wondering is that this is MQ 7.0.0.0 whether there is any bug. |
I don't run x.0 version of any software if it can be avoided.
| Quote: |
| We saw ( by accident while checking other stuff) that, there are about 12k message stuck in our SCTQ at both of our FR |
Pick up 2  and walk over to the guys in charge of MQ monitoring over there. You should have been paged when that queue backed up and stayed backed up.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Dec 21, 2009 6:31 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| PeterPotkay wrote: |
If the channels to QMx were Inactive
AND
There were messages to QMx in the S.C.T.Q.
AND
You have provided all the releveant info
AND
There are no other errors messages
then it smells like a bug to me.
| Quote: |
| The only thing I am wondering is that this is MQ 7.0.0.0 whether there is any bug. |
I don't run x.0 version of any software if it can be avoided.
| Quote: |
| We saw ( by accident while checking other stuff) that, there are about 12k message stuck in our SCTQ at both of our FR |
Pick up 2 and walk over to the guys in charge of MQ monitoring over there. You should have been paged when that queue backed up and stayed backed up. |
Thanks Peter.
I appreciate your very analytical way of looking things( although people say the days of analytical thinking are over. Now we are in the age of hunch ( blink-> enabled by quantum mechanics) or lateral thinking - see Edward De Bono)
Our monitoring system is evolving. still having a lot of issue with ITCAM( Tivoli).
I agree with you 100%. As I said earlier, we are guessing it may be a bug in 0.0.0 version and there might be a fix already in 7.0.1.0. I wanted to see if there is any other problem( again my guess is wrong information in FR about PR) or any other.
I have communicated with IBM. I am waiting to hear from them. |
|
| Back to top |
|
|
|
|
