Fixes are available
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
J2CA0041E exceptions may occur, when ComponentMetaData instance is set to null in the method getObjectInstance. The exception stack-trace is as following: [6/15/16 10:53:29:936 EEST] 00000198 ConnectionFac E J2CA0041E: The ComponentMetaData instance was null in method getObjectInstance. [6/15/16 10:53:29:944 EEST] 00000198 JDBCRA001 1 com.ibm.j2ca.base.WBIResourceAdapter endpointActivation(MessageEndpointFactory,ActivationSpec) Endpoint activation failed javax.resource.ResourceException: Failed to establish event manager at com.ibm.j2ca.base.WBIResourceAdapter.createEventManager (WBIResourceAdapter.java:508) Final CausedBy: Caused by: java.lang.IllegalStateException: Null ComponentMetaData at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getCMConfigData (ConnectionFactoryBuilderImpl.java:798) at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance (ConnectionFactoryBuilderImpl.java:453) at org.apache.aries.jndi.ObjectFactoryHelper.getObjectInstance UsingObjectFactoryBuilders(ObjectFactoryHelper.java:351) at org.apache.aries.jndi.ObjectFactoryHelper.getObjectInstance (ObjectFactoryHelper.java:109) at org.apache.aries.jndi.OSGiObjectFactoryBuilder.getObject Instance(OSGiObjectFactoryBuilder.java:62) at javax.naming.spi.NamingManager.getObjectInstance (NamingManager.java:349) at com.ibm.ws.naming.util.Helpers.processSerializedObjectFor LookupExt(Helpers.java:993) ... 85 more
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM WebSphere Application * * Server JCA/J2C component. * **************************************************************** * PROBLEM DESCRIPTION: Under rare circumstances * * ComponentMetaData can fall out of * * sync, ultimately leading to a * * NullPointerException in code that * * tries to check the ComponentMetaData. * **************************************************************** * RECOMMENDATION: * **************************************************************** In the ConnectionFactoryBuilderImpl.getCMConfigData when the ComponentMetaData (CMD) is null, an IllegalStateException is thrown.
Problem conclusion
This APAR changes the behavior of getCMConfigData to tolerate null CMD instead of throwing an IllegalStateException. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.12 and 9.0.0.3. 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
PI66697
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-08-01
Closed date
2016-12-13
Last modified date
2016-12-13
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
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022