high amount of amqcrsta processes

[tgdscer2]

Hi
We have an MQ Manager (5.2) on AIX (4.3.3) with about 20 client connection channels. We use the inet demon instead of the mq listener program. Because of the high usage of paging space we saw that there are a lot of amqcrsta processes which seems to be active. But verifying the date, most of them seems to be not used anymore. What can we do to decrease this amount of processes or do we have to inform our developpers to change their applications?
Thanks in advance
tgdscer2

 

[mqonnet]

If you say that you are using SVRCONN channels then i would say that your application programmers or at least some of the apps are not disconnecting properly which is why so many of the svrconn channels lying around.

I am not sure, but you could check the docs to see if changing maxactivechannels attribute in the mqs.ini file would make any difference in this case. It does when you have regular channels(sdr/rcvr), pretty much sure that it does for svrconn as well.

This attribute sets the maximum active channels at any point in time. Hence your apps cannot get a connection when you have more of them running or rather lying around doing nothing. Then you can end/kill them off.

Cheers.
KK

 

[tgdscer2]

Well, what can I suggest to the programmers? Is it correct that the applications have to terminate with MQCLOSE and MQDISC? This what I recommended to the programmers. When I define a value for maxactivechannels, then the queue manager won't accept anymore connections.
Thanks

 

[mqonnet]

All applications must end only after they have closed and disconnected from the queue and qm respectively. You have to also handle the situation of qmgr quiescing. Other than that i dont see much to be done in this area.
Cheers
KK

 

[541477]

Hi
We have an MQ Manager (5.3) on windows 2000 professional with about 2 connection channels. we saw that there are a lot of processes which seems to be active,such as amqzllp0.exe
amqzxma0.exe
amqzlaa0.exe
amqzfuma.exe
amqxssvn.exe(3)
amqsvc.exe
amqrrmfa.exe
amqxssvn.exe
amqmtbrn.exe
amqmhasmn.exe.
What can we do to decrease this amount of processes and what are they for?

Thanks
wyss

 

[mqonnet]

There is nothing you can do about these processes. These are MQ processes and need to be there all the time. Like, amqzllp0.exe, is the checkpoint processor that checkpoints all information at regular intervals pertaining to the happennings within the queue manager.


I dont think these process would be causing any issue to either the application programmer or to win2k.

Whats the issue, any ways.

Cheers
KK

 

[nedf]

Yo people,
Just to clarify a few things:
- MQ is made up of those processes listed above (about 10), so that is normal
- the amqcrsta process is the MQ listener program usually started by inetd
- there is a known issue with it since 5.1 that is still around and that is the multiple copies of it hanging around(I have hit 600 so far
- problem usually occurs when MQ dies for whatever reason and the listener keeps trying to accept connections, but MQ is down so it never completes its task and hangs around
- in the mean time the other side is retrying to connect so the first machine fires up another amqcrsta process to accept the connection . . . and away you go

Best thing to fix this issue is to :
- set the KeepAlive parameter to Yes in the qm.ini
- launch the listener via a script from inetd.conf, script checks if MQ is running and then runs the listener, otherwise just exits and does nothing.

Hope this helps,
Ned

 

[jomonpc]

I do face same problem. But these days we have limited the number of maximum client connection to 150 by adding these line in mqs.ini file
Channels:
MaxChannels=150
MaxActiveChannels=150
Also we close client connections by force when we max out by
stop chl(SYSTEM.DEF.SVRCONN) mode(force) in runmqsc.
This will take a few minutes depending on number of connections available. Last option is to restart Qmanager .