What could limit the number of client connections from WebSphere Port Listeners to MQ Server?
In WAS I setup around 24 Port Listeners with same Queue Connection Factory using client connection for a remote MQ server using a svrconn channel.
1/3 of listeners would start fine, but the rest are getting this:
AMQ9204: Connection to host 'host(1414)' rejected.
AMQ9558: The remote channel 'CH_SVRCONN' on host '' is not currently available.
MQ server is version 6.1 and not sure which configuration would determine the channel limit or how to check.
Any help or suggestions greatly appreciated.
This topic has been locked.
7 replies Latest Post - 2013-02-27T15:12:12Z by Steola
Pinned topic Some WAS Port Listeners fail connect to MQ using client connection
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-27T15:12:12Z at 2013-02-27T15:12:12Z by Steola
Re: Some WAS Port Listeners fail connect to MQ using client connection2013-02-25T19:49:47Z in response to Steolaadded this in qm.ini file and it did make a difference.
MaxChannels = 200
Either the value or the fact that i restart MQ Queue Manager. There was no such entry, which i thought would default to 100 channels, that should be enough for 24 listeners each one single threaded...
Re: Some WAS Port Listeners fail connect to MQ using client connection2013-02-27T15:12:12Z in response to SystemAdminI assume these are CC and RC in following
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2537;AMQ9204: Connection to host 'XXX(1414)' rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2537;AMQ9558: The remote channel 'XXXX_SVRCONN' on host '' is not currently available. http://3=XXXX_SVRCONN]],3=hskda001(1415),5=RemoteConnection.analyseErrorSegment