| Author |
Message
|
| madhead |
 Posted: Fri May 10, 2002 3:28 am Post subject: |
 |
|
Newbie
Joined: 14 Nov 2001
Posts: 5
|
I have MQ ver 5.2.1 with CSD04 running on a windows 2000 advanced server.
The amqzlaa0.exe processes continually increase until the QMGR dies and it has to be restarted. I have monitored the processes and they are gradually increasing at a rate of 8 about every 14 hours. I have been unable to simulate this on test machines.
Can anyone please help or at the very least point me in the right direction? |
|
| Back to top |
|
 |
| dgolding |
| Posted: Fri May 10, 2002 6:25 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
These are application agents - they are processes which interface your application to MQ, for protection. It sounds as if your application is spawning processes continously and not exiting properly.
|
|
| Back to top |
|
|
| madhead |
| Posted: Fri May 10, 2002 6:51 am Post subject: |
|
|
Newbie
Joined: 14 Nov 2001
Posts: 5
|
Is it possible to monitor which application is causing this error... without loading up the machine in the process?
(I only get this problem in production and not in development or test).
Thanks for the response!
Andy |
|
| Back to top |
|
|
| madhead |
| Posted: Fri May 10, 2002 6:53 am Post subject: |
|
|
Newbie
Joined: 14 Nov 2001
Posts: 5
|
| Also we have some VB components in COM+ is it possible that these are the problem? |
|
| Back to top |
|
|
| mqonnet |
| Posted: Fri May 10, 2002 7:30 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
For each application process that does an MQCONN, an Agent is created. And if you see many such applications, that means that there are many apps that are connected to your QM. If your app dies without properly disconnecting from the QM, then the chances of Agent hanging around is large.
What happens if you run the same app in your production machine, where you say you did not see the same problem happen.
But otherwise, as per my knowledge you cannot monitor an Agent process. Reason being, this is created by the QM and is internal to MQ. The other thing to check out would be to run the same app which is causing the problem on Production system to see if you get the same error back.
Even if there are many such agents, MQ would never be affected. Even though processing might get a bit slow(since each agent needs to process requests).
Hope this helps.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| madhead |
| Posted: Fri May 10, 2002 8:34 am Post subject: |
|
|
Newbie
Joined: 14 Nov 2001
Posts: 5
|
Kumar,
MQ is affected by the number of agents i.e. when the machine runs out of memory when there are too many agents in existence. MQ Dies, not completely, but a bit at a time and in any case I have to restart it and get rid of all the additional processes.
From your statement would I be correct then in assuming that I could safely kill off the orphaned processes then? In addition is it possible to put a time out on the amqzlaa0.exe process so that when no activity has occurred within a given time it cleans itself up?
I have not been able to get the problem on any machine except the production server. But I have a couple of more applications to try before I know for sure. It could be the number of simultaneous uses as that is difficult to simulate in test. I'll try that out though and get back to you.
Regards,
Andy
|
|
| Back to top |
|
|
| mqonnet |
| Posted: Fri May 10, 2002 8:40 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Yes. Any Agent that is idle or not being used could easily be killed/discarded. Usually there is ALWAYS at least 1 Agent that is in idle state.
As for the timeout on an Agent is concerned, i dont think it is possible. Reason. This is not controlled by application, but MQ. And MQ decides on it. The only way in which the app can have control on it is by disconnecting from the Qm. This way the agent dies..
Coming to memory consumption. Yes. Agents consume memory and also cpu time. And hence as i mentioned earlier, performance degradation is possible. But otherwise, having many agents has no effect whatsoever.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| mrlinux |
| Posted: Fri May 10, 2002 9:04 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
There are some tuning parameters for controlling the agents as far threads per agent (1 thread=1 app) so you can have mnay apps and only one agent.
MQSeries version 5.1 and greater automaticly have the threaded agents enabled
but you can still control the number of threads per agent. However if you have a app bug spawning threads, then all this will do is slow it down.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
|
|
