| Author |
Message
|
| dcjs |
 Posted: Sat Feb 09, 2008 5:36 pm Post subject: Queue Manager Got Locked |
 |
|
Acolyte
Joined: 10 Nov 2006
Posts: 53
Location: IBM Bangalore
|
We have MQ 5.3 on AIX and the queue manager got hanged that means whenever i issue
runmqsc QM
dis ql(BR2.IN) it gets hanged there is no reply.
When i saw the erros in /var/mqm/errors i found websphere MQ semaphore is busy.
and i we observed the disk usage on var/mqm as 97% used.
all the messages on queue are non persistent.
if i stop and start the queue manager all the messages will be lost.
If i want to alter the queue properties i can't because all runmqsc commands are hanging .
can anyone suggest me how to overcome this situation.
_________________
TRY TRY UNTIL U SUCCEED |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Sat Feb 09, 2008 6:17 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Sounds like you are pretty much done.
WMQ5.3 is no longer supported unless you have purchased extended support.
From your description it appears that some application has open to many connections to the MQManager or there is some shared memory conflict.
Non-Persistent messages are not written to disk so they can't be recovered even if you are using linear logging.
Indeed if you stop and restart the MQManager all the messages will be lost but you will restore service.
Looking forward to overcome this situation you may want to re-evaluate whether or not the messages in question are important enough to be persistent.
Hope this helps.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| dcjs |
| Posted: Sat Feb 09, 2008 7:03 pm Post subject: |
|
|
Acolyte
Joined: 10 Nov 2006
Posts: 53
Location: IBM Bangalore
|
Thanks for the reply.
we extended our support to MQ 5.3.
But could you please suggest me the best practices what need to be done.
If i stop and start the Queue Manager messages willbe lost and i cannot change the queue properties(to make it persistent).
Do you think that start and stop of the queue manager is the solution for this.
_________________
TRY TRY UNTIL U SUCCEED |
|
| Back to top |
|
|
| csmith28 |
| Posted: Sat Feb 09, 2008 8:02 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
I think you will have to add this experience to your lessons learned column.
As far as what needs to be done... The nicest way I can put this is to say that IBM has documented the difference between persistent and non-persistent messages.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Feb 09, 2008 10:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| dcjs wrote: |
| and i we observed the disk usage on var/mqm as 97% used. |
This is not good. Usually you start having problems with MQ when you go over 80% used. May I suggest that the first thing you do is add more space to the volume. Don't know if this is possible without stopping the qmgr... that's a question for your OS admin.
And of course kill those runaway runmqsc processes or have them killed...
For the rest see the comments above...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dcjs |
| Posted: Sun Feb 10, 2008 6:42 am Post subject: |
|
|
Acolyte
Joined: 10 Nov 2006
Posts: 53
Location: IBM Bangalore
|
I suggested system adminstrator to increase the space for var/mqm .
to affect this change we need to stop/start the queue manager because the previous messages are still not processed.
_________________
TRY TRY UNTIL U SUCCEED |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Feb 10, 2008 7:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can write a simple app that will get all messages from a queue, and put them to another queue, but as persistent messages instead of non-persistent messages.
You want to only do this for your application messages, though. Any messages that are on any SYSTEM queues, except maybe SYSTEM.DEAD.LETTER.QUEUE, should be left alone.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| boca1 |
| Posted: Sun Feb 10, 2008 10:50 am Post subject: |
|
|
Newbie
Joined: 10 Feb 2008
Posts: 2
|
we tried saving the messages using mqcapture utility(in RFHUTIL) but we are not able to connect to the queue.All the queues have gone down.
if i try to see the queue properties using Runmqsc and dis ql(*) the system is getting hanged) |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Feb 10, 2008 1:34 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| boca1 wrote: |
| we tried saving the messages using mqcapture utility(in RFHUTIL) but we are not able to connect to the queue.All the queues have gone down. |
Pedantically I repeat that you connect to a queue manager not to a queue, and it's the queue manager that runs (and in this instance goes down) not queues.
| boca1 wrote: |
if i try to see the queue properties using Runmqsc and dis ql(*) the system is getting hanged) |
Touching on the first point, playing with the queue (and changing the queue persistence to persistent) won't help. It's the default persistence and all the messages already have their persistence set.
You could try using runmqsc to change the max channels on the queue manager and then connect to remove the messages as suggested above. I'd have thought the problem is that the queue manager's run out of resource rather than hit a limit so I would be highly surprised if that works.
As has been commented before, you're done. Chalk it up to experience and remind the designers that messages which can't be reproduced need to be persistent.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Feb 10, 2008 5:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| dcjs wrote: |
I suggested system adminstrator to increase the space for var/mqm .
to affect this change we need to stop/start the queue manager because the previous messages are still not processed. |
Your reason for starting / stopping the qmgr have nothing to do with adding some space to the volume...or else your command of the English language could be better...
Remember that the primary reason you may have problems is because you don't have enough space on the volume... So if you can fix the space problem without stopping the qmgr you might be able to do something with all those messages...
As an alternate try using a tool like MO71 to download the messages to disk. You should be able to upload them after the qmgr is back up.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ashu |
| Posted: Sun Feb 10, 2008 9:55 pm Post subject: |
|
|
Centurion
Joined: 11 Nov 2006
Posts: 132
|
| fjb_saper wrote: |
As an alternate try using a tool like MO71 to download the messages to disk. You should be able to upload them after the qmgr is back up.
Enjoy |
I think if you are able to browse the messages on local Q using as simple a command as amqsbcg then you should be able to download them as well... as suggested by fjb_saper... 
_________________
Ashu
"It is simple to be Happy but difficult to be Simple" |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 11, 2008 1:13 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ashu wrote: |
| fjb_saper wrote: |
As an alternate try using a tool like MO71 to download the messages to disk. You should be able to upload them after the qmgr is back up.
Enjoy |
I think if you are able to browse the messages on local Q using as simple a command as amqsbcg then you should be able to download them as well... as suggested by fjb_saper... |
Every command, no matter how simple, requires a connection to the queue manager. If RFHUTIL doesn't work (as indicated in an earlier post) then nothing's going to work.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| UglyAngelX |
| Posted: Mon Feb 11, 2008 8:57 am Post subject: |
|
|
Voyager
Joined: 04 Dec 2001
Posts: 90
Location: BEARS FAN IN STEELER COUNTRY
|
| Since you are paying for extended support, why not use it and see if IBM has a solution for you? |
|
| Back to top |
|
|
| dcjs |
| Posted: Mon Feb 11, 2008 5:47 pm Post subject: |
|
|
Acolyte
Joined: 10 Nov 2006
Posts: 53
Location: IBM Bangalore
|
I think IBM support is not that much good because they keep on asking the information but it takes a long time to reply back.
But event then we raised a PMR.
_________________
TRY TRY UNTIL U SUCCEED |
|
| Back to top |
|
|
|
|
