| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| amq* executables not cleaning-up? |
« View previous topic :: View next topic » |
| Author |
Message
|
| mikehkk |
 Posted: Thu Jan 26, 2006 8:42 am Post subject: amq* executables not cleaning-up? |
 |
|
Apprentice
Joined: 29 Jul 2002
Posts: 25
|
We have MQSeries 5.2 & WebMQ 5.3 servers both running on various machines in a Win2000 environment. I wanted to describe something and see if it's "normal" behavior or not.
On a typical app server our ours, we have VB apps that continually poll/consume messages from various queues and then forward responses on different queues in a clustered queue manager environment. If you go to Processes tab of Task Manager on an app server while the VB apps are running, it's typical to see 50+ amq* executables of various types running. Interestingly, if you then turn all the VB applications off, basically the same set of 50+ amq* executables stick around. Only when you stop the MQ service entirely at this point does this number of amq* processes then go down to only about two or three (and release a huge chunk of memory in the process - more than a hundred MEG in the case of our app servers).
If you then immediately restart the MQ service - without VB apps running at this point - the number of amq* processes will jump, but no where near the 50+ that remained running immediately after the VB apps were first turned-off.
Concern: We're investigating a memory issue in our environments anyway.
Question: Does what I describe point to a faulty cleaning-up of processes on the part of MQ? (seems a consistent issue for both 5.2 and 5.3 servers running under the same OS/set of upgrades & SP's). Could this be a problem of MQ's interaction with the OS or one of the jillion MS security patches that have to be continually applied?
Appreciate any and all thoughts on the matter.
Mike Howard
michael.howard@pmigroup.com |
|
| Back to top |
|
 |
| mvic |
| Posted: Thu Jan 26, 2006 9:01 am Post subject: Re: amq* executables not cleaning-up? |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| mikehkk wrote: |
| it's typical to see 50+ amq* executables of various types running. Interestingly, if you then turn all the VB applications off, basically the same set of 50+ amq* executables stick around. Only when you stop the MQ service entirely at this point does this number of amq* processes then go down to only about two or three (and release a huge chunk of memory in the process - more than a hundred MEG in the case of our app servers) |
Depends exactly what those processes are. Are they amqzlaa0 ? These are processes hosting the queue manger threads that act on behalf of your apps. Although I daresay there is some algorithm dictating a cleanup strategy for unused processes, it isn't published as far as I know.
amqzlaa0 processes may not be cleaned up straight away, but they do get re-used by new apps. It is not clear to me why you want these processes to go away - they are doing no harm.
Bear in mind also, that as long as one app is being served by any given amqzlaa0 (each one is capable of serving 10s of apps) it cannot be cleaned up. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Jan 26, 2006 4:35 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
How many QMs on the server?
Do the VB apps connect in bindings mode, or as clients?
When you "turn off" the VB apps, do they MQCLOSE and MQDISC every connection they have made?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| terrir |
| Posted: Tue Jan 31, 2006 11:33 am Post subject: AMQZLAA0.EXE LOOPING |
|
|
Novice
Joined: 11 Jan 2006
Posts: 16
|
We upgraded our Window 2003 boxes to V6.0 and found that on our virtual server we have AMQZLAA0.EXE consuming a lot of the kernal.
Has anyone else had this problem?
Thanks |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Jan 31, 2006 12:16 pm Post subject: Re: AMQZLAA0.EXE LOOPING |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| terrir wrote: |
We upgraded our Window 2003 boxes to V6.0 and found that on our virtual server we have AMQZLAA0.EXE consuming a lot of the kernal.
Has anyone else had this problem? |
My first thought is : what is "a lot" ? My second thought is, what type of MQ work, and how much MQ work, is this system doing?
These processes perform most of the normal work of the queue manager on behalf of apps. On a busy queue manager (lots of puts / gets) the amqzlaa0 process(es) will register significant CPU and probably quite a lot of disk I/O as well. Could it be that there is actually no problem - it's just that your system is busy? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
