A fix is available
APAR status
Closed as program error.
Error description
Following exception is logged in the WebSphere Application Server V7.0 SystemOut.log when connecting to Active MQ: J2CA0046E:Method createManagedConnectionWithMCWrapper caught an exception during creation of the ManagedConnection for resource TopicConnectionFactory, throwing ResourceAllocationException. Original exception: <=================================>Exception Message -> null java.lang.NullPointerException at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection .java:39 1) at com.ibm.ejs.jms.JMSManagedTopicConnection.<init>(JMSManagedTopic Connecti on.java:74) at com.ibm.ejs.jms.GenericJMSManagedTopicConnectionFactory.createMa nagedCon nection(GenericJMSManagedTopicConnectionFactory.java:91) at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnect ion(JMSM anagedConnectionFactory.java:678) at com.ibm.ejs.j2c.FreePool.createManagedConnectionWithMCWrapper(Fr eePool.j ava:2086) at com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java :1761) at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2636) at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionMa nager.ja va:1064) at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionM anager.j ava:701) at com.ibm.ejs.jms.JMSTopicConnectionFactoryHandle.createTopicConne ction(JM STopicConnectionFactoryHandle.java:91) at darwin.pushport.web.PushportReceiver.doGet(PushportReceiver.java :55) The exception is not very helpful in determining the root cause as the actual exception is not traced in the above stack.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users of JMS * **************************************************************** * PROBLEM DESCRIPTION: A NullPointerException occurs during * * the * * JMSManagedConnection constructor. * **************************************************************** * RECOMMENDATION: * **************************************************************** If an Exception occurs during the JMSManagedConnection constructor a coding error may cause a NullPointerException to occur in the constructor which results in the original Exception information being discarded and unavailable for problem diagnosis. Typically the original Exception occurs due to a configuration error while obtaining the real ConnectionFactory from the JMS provider the first time a JMS connection for the ConnectionFactory is requested. The issue is already fixed in WebSphere Application Server version 8.5 and later releases.
Problem conclusion
The exception handling in the JMSManagedConnection constructor was fixed so that the NullPointerException no longer occurs, the original Exception is written to FFDC and is set as the cause of the javax.resource.ResourceException thrown from the method. This enables the root cause of the problem to be identified. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.15. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI89128
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-10-19
Closed date
2018-04-16
Last modified date
2018-04-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 October 2021