Check for new replies
Thread Rating:
  • 83 Vote(s) - 2.98 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Introduction to Queue Manager Processes
A Qmgr has a number of processes associated with it for various purposes. Some of these if crashed will affect the state of qmgr very badly and might result in the crashing of the qmgr. Some other processes can be stopped and started depending on the need. MQ admins should be knowing what each process are what it does for effectively monitoring the health of a queue manager.

In live environments, the monitoring tools will be used to monitor these processes which will generate alert to inform the support team if these processes are down. Support team can choose to take the necessary step by starting the processes or restarting the queue manager.

Check the processes for a queue manager "Test" in unix.
ps -ef | grep Test
  • amqzxma - Execution Controller
  • amqrrmfa - Repository processes
  • amqrmppa - Channel Pooler
  • amqzmur0 - Restartable processes (Responsible for logging transactions)
  • amqzmuc0 - Critical processes (Responsible for logging transactions)
  • amqzlaa0 - Queue Manager Agents
  • amqzdmaa - Deferred Message Processor
  • amqzfuma - OAM process
  • runmqchi - Channel Initiator
  • runmqlsr - Listener Process
  • amqpcsea - PCF Command Server

It is the first process which starts when a queue manager starts(it's PID will be 1).

  1. It spawns the other necessary processes for the queue manager.
  2. It periodically checks the health of other child processes
  3. It cleans up the child processes when queue manager ends

It is the process which handles cluster related activities in MQ.
Repository related information is stored in the form of messages in the queue SYSTEM.CLUSTER.REPOSITORY.QUEUE. "amqrrmfa" process is responsible for updating information in this queue as well as retrieving information from it.
Click Here to know more about it and the implications of it crashing.

It is a threaded process. By default, it can have up to 64 threads and it will create more amqrmppa process(which will also has 64threads) when request increases.
Channel Pooler process reuses its threads and also it will be running for sometime even when the requests ends and requirement is not there. This is for optimizing the performance.

Responsible for logging transaction information into log files.

Responsible for logging transaction information into log files.

It is the agent process or LQM agent process for the queue manager.
This agent process provides separation between Qmgr and Non-Fast Path or standard Applications that are connecting to the queue manager. This will provide security and stability to the queue manager at the cost of performance overhead. In other words, Agent process act as agents between the connecting application and the queue manager.

Agent process is a threaded process just like Channel Pooler process. It has 64 threads by default which can be used for 64 application connections and new threaded process will be spawned once more application connections come in. Queue manager reuses the pool of agent process threads just like channel pool threads.

Its is the deferred message handler process which processes messages from SYSTEM.PENDING.DATA.QUEUE.

It takes care of the OAM(Object Access Manager) related functionalities of the queue manager.
Click Here to know more about OAM in Queue Manager.

It is the channel initiator process for the queue manager which is responsible to trigger start the sender channels. It will listen to SYSTEM.CHANNEL.INITQ for trigger messages.

It is the listener process for the queue manager. It associates a port with the queue manager and opens it for other application in a network to connect to the queue manager.

It is the PCF command server which is used for handling remote administration requests. Command Server process will be listening to SYSTEM.ADMIN.COMMAND.QUEUE and expects commands as PCF(Programmable Command Format) messages.

Check for new replies

Forum Jump:

Users browsing this thread: 1 Guest(s)