| Author |
Message
|
| craig0 |
 Posted: Mon Jun 11, 2007 6:24 am Post subject: MQ 5.1 for NSK (Tandem) - Memory Leak in MQLQMAG |
 |
|
Novice
Joined: 11 Jun 2007
Posts: 17
|
IBM has identified a memory leak in MQLQMAG (fixed in CSD03). I have several running instances of this object, one in particular is consuming almost 1GB of SWAP. Can this process be stopped without any adverse impact to the Queue Manager??
Basically what is this process used for?
Thanks,
Craig |
|
| Back to top |
|
 |
| LuisFer |
| Posted: Mon Jun 11, 2007 10:12 am Post subject: Re: MQ 5.1 for NSK (Tandem) - Memory Leak in MQLQMAG |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
The MQLQMAG is the relation MQ==> Local application for APIs (MQGET,MQPUT,MQINQ,....)
If you stop a MQLQMAG process the application conected by this one received a 2009. No other problems with the rest of processes.
From manual
| Quote: |
The Local Queue Manager Agents (LQMA) perform the operations required to
process MQI calls on behalf of applications. The Agents execute the bulk of the
code that supports the MQI. The primary purpose of the agent is to separate
application programs from the queue manager’s critical resources, to protect
against rogue or malicious applications.
The number of agent processes depends on the number of connected applications
and the MinIdleLQMAgents specified in the QMINI file. When the queue manager
starts, each Execution controller will start the specified number of idle agents. As
agents become active, the Execution Controller starts new agents to maintain the
minimum number of idle agents. |
|
|
| Back to top |
|
|
| craig0 |
| Posted: Tue Jun 12, 2007 7:48 am Post subject: |
|
|
Novice
Joined: 11 Jun 2007
Posts: 17
|
Thanks for the info...I should have RTFM 
One question for you....So if I stop the agent process through which the application is making MQI calls would the application have to make another MQCONN call to reestablish communication with the Queue Manager?
Is it the LQMAG process that is returned to the application after the MQCONN call
What is a 2009 error?
Thanks,
Craig |
|
| Back to top |
|
|
| craig0 |
| Posted: Tue Jun 12, 2007 8:11 am Post subject: |
|
|
Novice
Joined: 11 Jun 2007
Posts: 17
|
I think I found my answer.....
MQRC_CONNECTION_BROKEN
(2009, X’7D9’) Connection to queue manager lost.
So it would seem the application would have to issue another MQCONN call to reestablish communication with the Queue Manager?
so the connection handle returned to the application on the MQCONN call is the LQMAG process?
Craig |
|
| Back to top |
|
|
| LuisFer |
| Posted: Tue Jun 12, 2007 10:19 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
| craig0 wrote: |
So it would seem the application would have to issue another MQCONN call to reestablish communication with the Queue Manager?
|
Yes , and don't forget re-Open the Queue.
| Quote: |
so the connection handle returned to the application on the MQCONN call is the LQMAG process?
|
No, the handle give it the QMgr (the MQS-ECBOSS server) |
|
| Back to top |
|
|
| craig0 |
| Posted: Tue Jun 12, 2007 12:12 pm Post subject: |
|
|
Novice
Joined: 11 Jun 2007
Posts: 17
|
ok and the EC boss assigns a LQMAG process to service the application calls?
| LuisFer wrote: |
| craig0 wrote: |
So it would seem the application would have to issue another MQCONN call to reestablish communication with the Queue Manager?
|
Yes , and don't forget re-Open the Queue.
| Quote: |
so the connection handle returned to the application on the MQCONN call is the LQMAG process?
|
No, the handle give it the QMgr (the MQS-ECBOSS server) |
|
|
| Back to top |
|
|
| LuisFer |
| Posted: Tue Jun 12, 2007 9:33 pm Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
| craig0 wrote: |
ok and the EC boss assigns a LQMAG process to service the application calls?
|
No, the sequence is ECBOSS => EC (Execution Controller) => MQLQMAG
The ECBOSS give the Handle and assing a EC (balancing CPU) and this one a MQLQMAG |
|
| Back to top |
|
|
|
|
