APAR status
Closed as program error.
Error description
When using the WebSphere MQ resource adapter inside WebSphere Liberty Profile, a NullPointerException originating within the internal method MQConnectionFactoryFactory.getObjectInstance() can occur when a JMS application performs a JNDI lookup.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of: - The WebSphere MQ V7.1 classes for JMS. - The WebSphere MQ V7.5 classes for JMS. - The WebSphere MQ V8 classes for JMS. - The WebSphere MQ V7.1 resource adapter. - The WebSphere MQ V7.5 resource adapter. - The WebSphere MQ V8 resource adapter. that have applications which look up Connection Factory definitions from a Java Naming and Directory Interface (JNDI) repository. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: In order to support JNDI lookups, the WebSphere MQ classes for JMS provide an internal class called MQConnectionFactoryFactory, which implements the JNDI ObjectFactory interface. When an application performs a JNDI lookup, the JNDI repository will call the method MQConnectionFactoryFactory.getObjectInstance(Object, Name, Context, Hashtable). If an application performed a JNDI lookup, and the JNDI repository called MQConnectionFactoryFactory,getObjectInstance(Object, Name, Context, Hashtable) passing in an object that was not a ConnectionFactory, the WebSphere MQ classes for JMS attempted to generate an FFDC as it did not recognize the type of object it had been given. While generating the FFDC, a NullPointerException was generated. The NullPointerException was returned to the application.
Problem conclusion
The WebSphere MQ classes for JMS have been updated so that they no longer try and generate an FFDC if the internal method MQConnectionFactoryFactory,getObjectInstance(Object, Name, Context, Hashtable) is called by a JNDI repository for an object that is not a ConnectionFactory. Instead, the method will return null back to the JNDI respository, which is the defined behaviour as documented in the JNDI Specification. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.1 7.1.0.7 v7.5 7.5.0.6 v8.0 8.0.0.4 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT08444
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
710
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-04-21
Closed date
2015-06-23
Last modified date
2015-06-23
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
WMQ WINDOWS V7
Fixed component ID
5724H7220
Applicable component levels
R710 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1"}]
Document Information
Modified date:
09 March 2021