Fixes are available
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
After a fix (fixpack or ifix) install, rollback or uninstall is performed, administrative scrips such as syncNode can fail if the if the OSGI bundle cache fails to be cleaned and is left in a stale state. The following error can be see when running the syncNode script after a fixpack update. [7/25/17 9:57:40:677 EDT] 00000001 AdminTool E ADMU0111E: Program exiting with error: java.lang.NoClassDefFoundError: com.ibm.ffdc.config.Formattable at java.lang.ClassLoader.defineClassImpl(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:346) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader. defineClass(Def aultClassLoader.java:188) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager. defineClass (Classpa thManager.java:580) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager. findClassIm pl(Class pathManager.java:550)Page 10 of 139 ... continues Caused by: java.lang.ClassNotFoundException: com.ibm.ffdc.config.Formattable at org.eclipse.osgi.internal.loader.BundleLoader. findClassInternal( BundleLo ader.java:506) at org.eclipse.osgi.internal.loader.BundleLoader.findClass (BundleLo ader.jav a:422) at org.eclipse.osgi.internal.loader.BundleLoader.findClass (BundleLo ader.jav a:410) ... 54 more This APAR will allow bootstrap code to check the WAS product version XML files for updates which will provide a more robust means of checking for a stale OSGi cache, allowing OSGI to proactively run in -clean mode. Updating this logic will make the changes applicable to syncnode in addition to all admin scripts.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Class loading failures occur in the * * OSGi framework after a fixpack or * * other maintenance package is applied * **************************************************************** * RECOMMENDATION: * **************************************************************** The OSGi framework that manages server class loading maintains a cache of bundle data and relationships. When modifications are made to the server's binaries, this cached data can become out of date, leading to failures in class loading. The cache is regenerated as part of the first server start following maintenance application, but other tools (such as syncNode) run prior to this first server start may fail.
Problem conclusion
Additional checking was added to more aggressively clean the OSGi framework cache after maintenance packages have been applied. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.13 and 9.0.0.7. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Run the osgiCfgInit.sh|bat script from the server or profile bin directory to clear the OSGi cache manually.
Comments
APAR Information
APAR number
PI86187
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
2017-08-21
Closed date
2018-01-24
Last modified date
2018-01-24
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