| Author |
Message
|
| shashivarungupta |
 Posted: Tue Jan 04, 2011 11:46 am Post subject: |
 |
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
ps -ef | grep mqm*
will list all the qmgr related processes (which are owned by mqm)
| Code: |
e.g.:
mqm 131090 254852 0 Dec 02 - 0:12 amqzmuc0 -m QMGR
mqm 180242 254852 0 Dec 02 - 0:15 /usr/mqm/bin/amqzdmaa -m QMGR
mqm 143630 271244 0 Dec 02 - 2:02 /usr/mqm/bin/amqrmppa -m QMGR
mqm 192944 254852 0 Dec 02 - 0:10 /usr/mqm/bin/amqzfuma -m QMGR
mqm 127734 254852 0 Dec 02 - 0:32 amqzlaa0 -mQMGR -fip0
mqm 139796 267146 0 Dec 02 - 0:09 /usr/mqm/bin/amqpcsea QMGR
mqm 189376 254852 0 Dec 09 - 0:03 amqzlaa0 -mQMGR -fip1042
mqm 254852 1 0 Dec 02 - 0:51 amqzxma0 -m QMGR
mqm 258950 254852 0 Dec 02 - 0:21 amqzmur0 -m QMGR
mqm 263048 254852 0 Dec 02 - 0:09 /usr/mqm/bin/amqrrmfa -m QMGR -t2332800 -s2592000 -p2592000 -g5184000 -c3600
mqm 267146 254852 0 Dec 02 - 0:04 /usr/mqm/bin/amqzmgr0 -m QMGR
mqm 271244 267146 0 Dec 02 - 0:07 /usr/mqm/bin/runmqchi -m QMGR -r
mqm 279440 267146 0 Dec 02 - 0:00 /usr/mqm/bin/runmqlsr -r -m QMGR -t TCP -p 1414
|
where you can see the qmgr pid (which is child of init process) is the parent process for the other process associated with it.
suppose when qmgr ends then its process should not be listed as running/active processes in the ps table. when the qmgr goes down its processes should go down too, logically. if they don't then something would've went wrong..that's why they might be present in ps table. (it was on aix about which I told, a scenario was being faced)
_________________
*Life will beat you down, you need to decide to fight back or leave it.
Last edited by shashivarungupta on Tue Jan 04, 2011 12:04 pm; edited 1 time in total |
|
| Back to top |
|
 |
| shashivarungupta |
| Posted: Tue Jan 04, 2011 11:55 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
And I meant to say by transactions 'that are long running transactions'. (which I agreed upon).
Am sorry to say that term which was used, not just by me.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 04, 2011 3:02 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| And I meant to say by transactions 'that are long running transactions' |
What will a reader better understand from this?
More precision is needed. The term transaction has too many meanings to be concise.
I can guess that you mean WMQ Units of Work. I can guess that you mean mqputs/mqgets done in syncpoint, and therefore logged.
As to the results of the ps -ef|grep mqm command, which processes can or should be killed? Which processes should not be killed? Is there a specific order in which processes should be killed? Which are zombies? Are any of these processes the transactions you refer to?
_________________
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 |
|
|
| mvic |
| Posted: Tue Jan 04, 2011 4:26 pm Post subject: Re: QM logs are full in windows MQ |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| suneel wrote: |
| at receiver side logs it is saying QM logs are full. Please help me on this. |
Please post the full error message you saw.
The error message should include a suggestion for what to try. Or maybe searching for the AMQnnnn number in the MQ Information Center will provide extra information. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed Jan 05, 2011 6:17 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| bruce2359 wrote: |
| Quote: |
| And I meant to say by transactions 'that are long running transactions' |
What will a reader better understand from this?
More precision is needed. The term transaction has too many meanings to be concise.
I can guess that you mean WMQ Units of Work. I can guess that you mean mqputs/mqgets done in syncpoint, and therefore logged.
As to the results of the ps -ef|grep mqm command, which processes can or should be killed? Which processes should not be killed? Is there a specific order in which processes should be killed? Which are zombies? Are any of these processes the transactions you refer to? |
Processes which are floating in ps table even when the qmgr is ended, should be killed., for normal start of the qmgr next time.
The order in which processes to be killed , is :
| Code: |
amqzmuc0 Critical process manager
amqzxma0 Execution controller
amqzfuma OAM process
amqzlaa0 LQM agents
amqzlsa0 LQM agents
amqzmgr0 Process controller
amqzmur0 Restartable process manager
amqrmppa Process pooling process
amqrrmfa The repository process (for clusters)
amqzdmaa Deferred message processor
amqpcsea The command server
|
reference : http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/fa22310_.htm
http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Jan 05, 2011 6:36 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| shashivarungupta wrote: |
...The order in which processes to be killed , is :
| Code: |
amqzmuc0 Critical process manager
amqzxma0 Execution controller
amqzfuma OAM process
amqzlaa0 LQM agents
amqzlsa0 LQM agents
amqzmgr0 Process controller
amqzmur0 Restartable process manager
amqrmppa Process pooling process
amqrrmfa The repository process (for clusters)
amqzdmaa Deferred message processor
amqpcsea The command server
|
reference : http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/fa22310_.htm |
| shashivarungupta wrote: |
| http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/ |
And if it is WMQ V7.0? I ask as the second link contains the text "...I thought it was worth highlighting that the order in which you stop the processes was changed for WMQ v6...", and if it changed for V6.0 it may well have changed for V7.0, and/or more processes may have been added that also need to be killed - and in the right order.
Yet again, a lack of clarity and specificity on your part.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed Jan 05, 2011 6:49 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| exerk wrote: |
| shashivarungupta wrote: |
...The order in which processes to be killed , is :
| Code: |
amqzmuc0 Critical process manager
amqzxma0 Execution controller
amqzfuma OAM process
amqzlaa0 LQM agents
amqzlsa0 LQM agents
amqzmgr0 Process controller
amqzmur0 Restartable process manager
amqrmppa Process pooling process
amqrrmfa The repository process (for clusters)
amqzdmaa Deferred message processor
amqpcsea The command server
|
reference : http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/fa22310_.htm |
| shashivarungupta wrote: |
| http://hursleyonwmq.wordpress.com/2007/03/22/stopping-queue-managers-when-nothing-else-will/ |
And if it is WMQ V7.0? I ask as the second link contains the text "...I thought it was worth highlighting that the order in which you stop the processes was changed for WMQ v6...", and if it changed for V6.0 it may well have changed for V7.0, and/or more processes may have been added that also need to be killed - and in the right order.
Yet again, a lack of clarity and specificity on your part. |
I gave the points/links above for MQ v6.0 ONLY.  (because in reference of what I faced THE issue in the past was on MQv6.0).
For More clarity I've provided the LINKS above that you can refer.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jan 05, 2011 6:53 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| shashivarungupta wrote: |
| Processes which are floating in ps table even when the qmgr is ended, should be killed., for normal start of the qmgr next time. |
How did we get into a subject like this? The OP's problem is a (so far, non-specific) example of logs filling up. I can't see any need to list MQ processes, suggest they be killed, etc.
Still hoping suneel will post the actual error message, in full. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Jan 05, 2011 6:55 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| shashivarungupta wrote: |
| I gave the points/links above for MQ v6.0 ONLY. (because in reference of what I faced THE issue in the past was on MQv6.0). |
Then state, unequivocally that they refer to that version! The only safe assumption that you should make is that someone may act on your advice, and that someone may not have the same depth of knowledge and assume that the advice given is applicable - and if that person is using a different version your advice may not only be non-applicable, but fatal 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed Jan 05, 2011 7:04 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| exerk wrote: |
| shashivarungupta wrote: |
| I gave the points/links above for MQ v6.0 ONLY. (because in reference of what I faced THE issue in the past was on MQv6.0). |
Then state, unequivocally that they refer to that version! The only safe assumption that you should make is that someone may act on your advice, and that someone may not have the same depth of knowledge and assume that the advice given is applicable - and if that person is using a different version your advice may not only be non-applicable, but fatal |
Oh Come on... i know...one must know the version ..then only the perfect solution can be given for the respective issue. And for that poster has to be clear too about what configuration he/she has on his/her system.
'A post being a critic is an easy job'.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed Jan 05, 2011 7:41 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| exerk wrote: |
| And if it is WMQ V7.0? I ask as the second link contains the text "...I thought it was worth highlighting that the order in which you stop the processes was changed for WMQ v6...", and if it changed for V6.0 it may well have changed for V7.0, and/or more processes may have been added that also need to be killed - and in the right order. |
In SystemAdminGuidev7.0 : Chapter11, Page 537: You can find this...
| Code: |
To stop a queue manager running under WebSphere MQ for UNIX systems:
1. Find the process IDs of the queue manager programs that are still running
using the ps command. For example, if the queue manager is called QMNAME, use
the following command:
ps -ef | grep QMNAME
2. End any queue manager processes that are still running. Use the kill command,
specifying the process IDs discovered using the ps command.
End the processes in the following order:
amqzmuc0 Critical process manager
amqzxma0 Execution controller
amqzfuma OAM process
amqzlaa0 LQM agents
amqzlsa0 LQM agents
amqzmuf0 Utility Manager
amqzmgr0 Process controller
amqzmur0 Restartable process manager
amqfqpub Publish Subscribe process
amqfcxba Broker worker process
amqrmppa Process pooling process
amqcrsta Non-threaded responder job process
amqcrs6b LU62 receiver channel and client connection
amqrrmfa The repository process (for clusters)
amqzdmaa Deferred message processor
amqpcsea The command server
runmqtrm Invoke a trigger monitor for a server
runmqdlq Invoke dead-letter queue handler
runmqchi The channel initiator process
runmqlsr The channel listener process
amqxssvn Shared memory servers
amqztrcn Trace
Note: Processes that fail to stop can be ended using kill -9.
If you stop the queue manager manually, FFSTs might be taken, and FDC files
placed in /var/mqm/errors. Do not regard this as a defect in the queue manager.
The queue manager should restart normally, even after you have stopped it using
this method.
|
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jan 05, 2011 7:46 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| 'A post being a critic is an easy job'. |
It's much easier to give false, misleading, unclear, thoughtless, irrelevant or dangerous, advice.
If you choose to post here, your posts are subject to the scrutiny of subject matter experts. I fully expect my posts to be critiqued by readers. I have learned much from this criticism, and I don't take it personally.
_________________
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.
Last edited by bruce2359 on Wed Jan 05, 2011 7:53 am; edited 1 time in total |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jan 05, 2011 7:50 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| I think the OP should start a new thread because this one has wandered off into some completely separate subject. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Jan 05, 2011 8:04 am Post subject: Cleanly starting a QMGR |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
|
| Back to top |
|
|
|
|
