Websphere MQ call failed with compcode '2' (MQCC_FAILED') reason '2537' ('MQRC_CHANNEL_NOT_AVAILABLE')

Issue

We are using Jboss EAP6.1 in our application where we deployed MDB and portlets. While doing performance testing and making concurrent connections to portal we figured out that On MQ server side channel is reaching max limit of connections and it is getting abnormally ended. But when we testing the our all portlets after stopping MDB components it ran successfully with 100 % load and concurrent connections. So it is quite evident the MDB configured in portal server is causing this issue. Error we are getting in MQ server is :

Websphere MQ call failed with compcode '2' (MQCC_FAILED') reason '2537' ('MQRC_CHANNEL_NOT_AVAILABLE')

Jboss server should handle the connections in optimum way as seems JBoss is holding the mq connections and on mq server side connections keep on increasing . When we tried to shutdown the Jboss server we can see dropping mq connections on MQ server side. For making mq connections form MDB we are using com.ibm.mq.jms.MQQueueConnectionFactory configured in side the MDB and also we are manually closing mq session and mq connections after pushing message into queue. We have configured wmq.jmsra.rar in standalone.xml and version of MQ server is 7.1.0.0. We are not using JNDI and no connection pool is defined for using jms connections. In Jboss 5.x these MDB components are working fine but when we are migrating components in Jboss 6.1.1 during the performance testing causing these issues.

This issue we are getting when mq connections reaching max limit on MQ server. We also increased the MAX connections on MQ to 400 but when connections reaching more than that getting the same issue.