Middleware News

MQ Manager stops responding to JMS requests. Symptom SystemOut.log: FreePool E J2CA0046E: Method createManagedConnctionWithMCWrapper caught an exception during creation of the ManagedConnection for resource JMS$cftestcf$JMSManagedConnection@1373738090, throwing ResourceAllocationException. Original exception: javax.resource.spi.ResourceAdapterInternalException: Failed to create session at com.ibm.ejs.jms.JMSCMUtils.mapToResourceException(JMSCMUtils.java:125) at com.ibm.ejs.jms.JMSManagedSession. (JMSManagedSession.java:213) . . . javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'xldn0384abc:XYZ123' at com.ibm.mq.jms.services.ConfigEnvironment.newException (ConfigEnvironment.java:546) at com.ibm.mq.jms.MQConnection.createQM (MQConnection.java:1450) at com.ibm.mq.jms.MQConnection.createQMNonXA (MQConnection.java:960) at . . . com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009 at com.ibm.mq.MQManagedConnectionJ11

In WebSphere Application Server, all JMS connection factories, including queue connection factories (QCFs) and topic connection factories (TCFs) have connection pool and session pool settings that can be configured. This technote explains the following points: The difference between these pools and their relationship The maximum number of TCP/IP connections to a WebSphere MQ queue manager that is expected with a given set of connection pool and session pool settings The manner in which these settings are affected when message listener ports are configured to use the connection factory Resolving the problem In the JMS programming model, an application must get a JMS connection and a JMS session to send a message. A typical JMS application that sends messages looks like this: QueueConnectionFactory qcf = (QueueConnectionFactory)ctx.lookup("jms/qcf"); Queue queue = (Queue)ctx.lookup("jms/q"); QueueConnection jmsconn = qcf.createQueueConnect