Fixes are available
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
A leak exists within the ZipFileArtifactNotifier class when a zip file is deleted from the dropins folder, causing all ZipFileArtifactNotifier instances to remain. When a zip file of the same name is re-added into the dropins folder, an IllegalStateException is thrown. . Exception = java.lang.IllegalStateException Source = com.ibm.ws.kernel.filemonitor.internal.MonitorHolder probeid = 721 Stack Dump = java.lang.IllegalStateException: [C:\Liberty\wlp\usr\servers\testServer\dropins\testFile.ear] at com.ibm.ws.artifact.zip.internal.ZipFileArtifactNotifier.onChang e(ZipFileArtifactNotifier.java:367) at com.ibm.ws.kernel.filemonitor.internal.MonitorHolder.scheduledSc an(MonitorHolder.java:718) at com.ibm.ws.kernel.filemonitor.internal.MonitorHolder.run(Monitor Holder.java:537) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja va:482) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask .java:362) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:189) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture Task.access$301(ScheduledThreadPoolExecutor.java:189) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture Task.run(ScheduledThreadPoolExecutor.java:304) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec utor.java:1156) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe cutor.java:626) at java.lang.Thread.run(Thread.java:780)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile that deploy * * application archives through the dropins * * folder. * **************************************************************** * PROBLEM DESCRIPTION: Deleting and re-adding the same zip * * application to the dropins folder can * * result in an IllegalStateException. * **************************************************************** * RECOMMENDATION: * **************************************************************** A leak exists within the ZipFileArtifactNotifier class when a zip file is deleted from the dropins folder, causing all ZipFileArtifactNotifier instances to remain. When a zip file of the same name is re-added into the dropins folder, an IllegalStateException is thrown. If the deletion and re-add occurs a second time, there will be two exceptions thrown. After the nth deletion/re-addition, there will be n exceptions thrown. Each IllegalStateException has the following stack dump: Exception = java.lang.IllegalStateException Source = com.ibm.ws.kernel.filemonitor.internal.MonitorHolder probeid = 721 Stack Dump = java.lang.IllegalStateException: [C:\Liberty\wlp\usr\servers\testServer\dropins\testFile.ear] at com.ibm.ws.artifact.zip.internal.ZipFileArtifactNotifier.onChang e(ZipFileArtifactNotifier.java:367) at com.ibm.ws.kernel.filemonitor.internal.MonitorHolder.scheduledSc an(MonitorHolder.java:718) at com.ibm.ws.kernel.filemonitor.internal.MonitorHolder.run(Monitor Holder.java:537) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja va:482) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask .java:362) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:189) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture Task.access$301(ScheduledThreadPoolExecutor.java:189) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFuture Task.run(ScheduledThreadPoolExecutor.java:304) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec utor.java:1156) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe cutor.java:626) at java.lang.Thread.run(Thread.java:780)
Problem conclusion
All listeners of each ZipFileArtifactNotifier instance are now properly tracked, so when they are removed due to the zip file deletion, the ZipFileArtifactNotifier is subsequently unregistered properly. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.5. 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
PI27843
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-10-17
Closed date
2014-10-23
Last modified date
2014-10-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
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
R855 PSY
UP
Document Information
Modified date:
28 April 2022