Posted: Sat Mar 24, 2007 10:29 am Post subject: Stress Test Issues; Establishing a TCP/IP Connection
Novice
Joined: 15 Aug 2006 Posts: 15
I'm a Java Developer and not a MQ Admin so my admin knowledge is limited. And from the intercommunication manuals I see that there are two ways to establish a TCP/IP connection namely :
a) Using inetd or
b) Using runmqlsr
My MQAdmin has done both in the above for the Queue Managers that I'm using. From this board/other resources I learnt that using runmqlsr is recommended over inetd for MQ v 5.3 and up. So the question is: i) Is it correct to use both ways (inetd and runmqlsr) for running a queue manager ? ii) If its ok to use inetd and runmqlsr then which one overrides what at runtime ?
I'm stress testing a client using WMQ Client to connect to the WMQ Server via a Server Connection Channel over JMS. On the WMQ Server node after stress tests I observed that there are approx. 70 amqcrsta processes running and during stress tests under peak load the Queue Manager becomes unresponsive and the client throws a 2059 error code (the # of amqcrsta processes under peak load haven't been recorded as of the last test).
Any possible leads where to start troubleshooting such an issue ?
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