Posted: Wed Aug 17, 2005 7:59 pm Post subject: Multiple amqzlsa0 processes on RHEL 3 & MQ 5.3 CSD10
Apprentice
Joined: 21 Oct 2002 Posts: 31
I am testing a RHEL 3 linux server with MQ 5.3 & CSD10 applied. Using the AMQ_THREADMODEL_RESET=1 env variable when installing MQ. Everything seems fine. However, when I run a simple java request/reply program on the same server (no channel definitions) we get multiple amqzlsa0 processes being spawned that "hang around" for quite a long time. If we run the java program multiple tiimes the # of amqzlsa0 processes can get as high as 250.
My questions:
What is amqzlsa0?
Is this behavior normal?
Will these process affect the system when load to other applications on the system is applied?
Is this a problem with the whole NPTL/Linux threads thing in RHEL 3?
amqzsla0 is the agent process that handles socket connections to the qmgr, when the app -> qmgr connection is set to isolated bindings.
It is used when the qm.ini Connection stanza contains the attribute DefaultBindType=ISOLATED.
This behaviour is not normal or desirable - it is a WMQ bug that setting the env var AMQ_THREADMODEL_RESET causes socket conections to be used instead of shared memory connections.
You should use LD_ASSUME_KERNEL=2.4.19 instead. _________________ MQSeries.net helps those who help themselves..
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