| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Websphere MQ Task |
« View previous topic :: View next topic » |
| Author |
Message
|
| yorch017 |
 Posted: Wed Nov 26, 2008 2:07 pm Post subject: Websphere MQ Task |
 |
|
Newbie
Joined: 26 Nov 2008
Posts: 2
|
I need help with AMQZXMAX task. I don't know, when and why it runs?  [/i] |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Nov 26, 2008 3:26 pm Post subject: Re: Websphere MQ Task |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| yorch017 wrote: |
| I need help with AMQZXMAX task. I don't know, when and why it runs? |
So do your diligence and find and describe the pid tree to get to that process.
It will become so much more clearer... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Nov 26, 2008 5:00 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
amqzxma0
This is the execution controller (EC) process, which is the heart of a queue manager. There is one per queue manager. When an application issues an MQCONN, a shared memory message is sent to this process to identify a handler agent process and it may launch a new agent for this request. All other queue manager system processes are child processes of amqzxma0.
_________________
Glenn |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 27, 2008 12:52 am Post subject: Re: Websphere MQ Task |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| yorch017 wrote: |
| I need help with AMQZXMAX task. |
Why? What ill effects are you seeing? Why are you interested?
In normal use, any of the AMQ* tasks are managed internally.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| yorch017 |
| Posted: Thu Nov 27, 2008 2:47 pm Post subject: |
|
|
Newbie
Joined: 26 Nov 2008
Posts: 2
|
| We use MQ for iSeries. We tried to execute a STRMQM and this command didn´t response (this problem is related with qmanager's journal, MQ didn`t recover any information from it), immediately the AMQZXMAX run, and it was using 65% of CPU. While the AMQZXMAX process was running we couldn´t execute any MQ command on another qmanager. The MQ was freeze. When we killed the AMQZXMAX process, MQ returned to the normally. |
|
| 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
|
|
|
|
