Fixes are available
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Environment Description: OS Level : AIX_2 (64bit) (Install Chinese OS) WAS Level : WebSphere Application Server Network Deployment edition V7.0.0.19 (32-bit) Enable Application Server Global/admin Security?: YES Web Server : IBM HTTP Server 7.0.0.19 DB Lever : Remote DB2 Ent 9.7 FP4 (64bit) Problem description: Customer ran automated deployment script and saw many errors as follows in the systemOut log: [11-10-13 15:13:01:603 GMT+08:00] 00000052 wtp E org.eclipse. jst.j2ee.commonarchivecore.internal.strategy.DirectoryLoadStrate gyImpl collectFilesFromBinaries Failed to extract binaries to temporary location: Binaries files were not added! Customer was able to reproduce this issue on the following WebSphere Application Server fix pack levels: 7.0.0.11, 7.0.0.17, 7.0.0.19, on three different operating systems: AIX, Solaris and Microsoft Windows.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server who update applications using * * wsadmin. * **************************************************************** * PROBLEM DESCRIPTION: Updating an application using wsadmin * * may cause an error message to * * be displayed in SystemOut.log. * **************************************************************** * RECOMMENDATION: The error messages can be safely ignored. * **************************************************************** After deleting a module from a deployed application, subsequent changes to that application may display the following error: org.eclipse. jst.j2ee.commonarchivecore.internal.strategy.DirectoryLoadStrate gyImpl collectFilesFromBinaries Failed to extract binaries to temporary location: Binaries files were not added! The error message is the result of the deleted module not having been marked as deleted. This causes an exception, which is caught and displayed. Processing continues correctly following the exception, and the application is updated successfully. The error message and the exception can be ignored.
Problem conclusion
The code has been updated to avoid the condition that caused the exception. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.25, 8.0.0.4, and 8.5.0.1. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Please note an interim fix will be provided under APAR PM68076.
Comments
APAR Information
APAR number
PM54006
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-09
Closed date
2012-02-03
Last modified date
2012-07-19
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
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
28 October 2021