Fixes are available
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
When installing a Resource Adapter (either standalone or embedded) which refers to classes and/or jars placed in the WAS_HOME/lib directory, a java.lang.NoClassDefFoundError exception will occur
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V8.0 users * * of Java Connector Architecture Resource * * Adapters * **************************************************************** * PROBLEM DESCRIPTION: Installing a Resource Adapter that * * accesses classes or jars in the * * WAS_HOME/lib directory fails with an * * exception * **************************************************************** * RECOMMENDATION: * **************************************************************** Resource Adapters can't access classes or jars in the WAS_HOME/lib directory. Attempting to install such a Resource Adapter will result in an exception similar to: [01/12/2010 11:27:41:515 CST] ADMA5006E: An error occurred configuring MyApplication in WebSphere Application Server repository: java.lang.NoClassDefFoundError: com.ibm.websphere.ffdc.FFDCSupport [01/12/2010 11:27:41:562 CST] java.lang.NoClassDefFoundError: com.ibm.websphere.ffdc.FFDCSupport [01/12/2010 11:27:41:562 CST] at java.lang.J9VMInternals.verifyImpl(Native Method) [01/12/2010 11:27:41:562 CST] at java.lang.J9VMInternals.verify(J9VMInternals.java:85) [01/12/2010 11:27:41:562 CST] at java.lang.J9VMInternals.verify(J9VMInternals.java:83) [01/12/2010 11:27:41:562 CST] at java.lang.J9VMInternals.initialize(J9VMInternals.java:162) [01/12/2010 11:27:41:562 CST] at java.lang.Class.forNameImpl(Native Method) [01/12/2010 11:27:41:578 CST] at java.lang.Class.forName(Class.java:168) [01/12/2010 11:27:41:578 CST] at com.ibm.ws.management.commands.jca.J2CCommandHelper.getIntrospec tedProps(J2CCommandHelper.java:1290) [01/12/2010 11:27:41:578 CST] at com.ibm.ws.management.commands.jca.J2CCommandHelper.getNewProper tyListFromComparison(J2CCommandHelper.java:169) [01/12/2010 11:27:41:578 CST] at com.ibm.ws.management.application.task.ConfigureTask.reconcileJ2 CObjects(ConfigureTask.java:876) [01/12/2010 11:27:41:578 CST] at com.ibm.ws.management.application.task.ConfigureTask.performTask (ConfigureTask.java:388) [01/12/2010 11:27:41:578 CST] at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImp l.java:315) [01/12/2010 11:27:41:578 CST] at java.lang.Thread.run(Thread.java:769) [01/12/2010 11:27:41:578 CST] Caused by: java.lang.ClassNotFoundException: com.ibm.websphere.ffdc.FFDCSupport [01/12/2010 11:27:41:578 CST] at org.eclipse.jst.j2ee.commonarchivecore.internal.util.ArchiveFile DynamicClassLoader.getClassInDependentJarInEAR(ArchiveFileDynami cClassLoader.java:586) [01/12/2010 11:27:41:578 CST] at org.eclipse.jst.j2ee.commonarchivecore.internal.util.ArchiveFile DynamicClassLoader.loadClass(ArchiveFileDynamicClassLoader.java: 254) [01/12/2010 11:27:41:578 CST] at java.lang.ClassLoader.loadClass(ClassLoader.java:627) [01/12/2010 11:27:41:578 CST] ... 12 more The exception may be either java.lang.NoClassDefFoundError or java.lang.ClassNotFoundException. The class name listed by the exception will vary depending on the Resource Adapter being installed. This is caused by the wrong class loader being used during installation of the Resource Adapter.
Problem conclusion
The Resource Adapter installation process was changed to use a classloader which has access to WAS_HOME/lib classes and jars. The fix for this APAR is currently targeted for inclusion in fix pack 8.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
PM58816
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-22
Closed date
2012-03-14
Last modified date
2012-03-14
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
28 October 2021