Fixes are available
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
When redeploying an application the application fails to restart reporting [ERROR ] CWWKE0701E: FrameworkEvent ERROR Bundle:gateway.bundle.EARApplication.MyApplication(id=200) java.io.IOException: Exception in opening zip file: C:\Users\myUser\Desktop\wlp\usr\servers\defaultServer\workarea\o rg.eclipse.osgi\bundles\200\1\bundlefile at org.eclipse.osgi.framework.util.SecureAction.getZipFile(SecureAc tion.java:291) at [internal classes] at com.ibm.cds.CDSBundleFile.getEntry(CDSBundleFile.java:95) at org.eclipse.osgi.baseadaptor.bundlefile.BundleFileWrapperChain.g etEntry(BundleFileWrapperChain.java:43) at [internal classes] Caused by: java.io.FileNotFoundException: C:\Users\myUser\Desktop\wlp\usr\servers\defaultServer\workarea\o rg.eclipse.osgi\bundles\200\1\bundlefile (The system cannot find the path specified.) Note, that the error also occurs when simply commenting out the application from the server.xml and then later re-enabling
Local fix
N.A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Core * **************************************************************** * PROBLEM DESCRIPTION: Application fails to restart, * * reporting FileNotFoundException * **************************************************************** * RECOMMENDATION: * **************************************************************** When redeploying an application on the Liberty profile it is possible that an IOException or FileNotFoundException will occur and the application will not start. Note that commenting out the application from the server.xml and later reactivating is the same as redeploying. The FileNotFoundException will be similar to: [ERROR ] CWWKE0701E: FrameworkEvent ERROR Bundle:gateway.bundle.EARApplication.MyApplication(id=200) java.io.IOException: Exception in opening zip file: C:\Users\myUser\Desktop\wlp\usr\servers\defaultServer\workarea\o rg.eclipse.osgi\bundles\200\1\bundlefile at org.eclipse.osgi.framework.util.SecureAction.getZipFile(SecureAc tion.java:291) at [internal classes] at com.ibm.cds.CDSBundleFile.getEntry(CDSBundleFile.java:95) at org.eclipse.osgi.baseadaptor.bundlefile.BundleFileWrapperChain.g etEntry(BundleFileWrapperChain.java:43) at [internal classes] Caused by: java.io.FileNotFoundException: C:\Users\myUser\Desktop\wlp\usr\servers\defaultServer\workarea\o rg.eclipse.osgi\bundles\200\1\bundlefile (The system cannot find the path specified.)
Problem conclusion
The problem occurs because the gateway bundle associated with the application's context classloader is uninstalled when the application stops, but the classloader is re-used when the application restarts. The (now stale) classloader refers to the missing bundle which can cause the IOException or FileNotFoundException. The correct and now modified behavior is to create a new classloader instance when the application restarts. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.2. 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
PI12116
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-02-19
Closed date
2014-03-17
Last modified date
2014-03-17
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
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
R855 PSY
UP
Document Information
Modified date:
27 April 2022