Fixes are available
PM91417;7.0.0: provide option for backwards compatibility for earexpander
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
PM91417;8.5.5: Provide option for backwards compatibility for earexpander
PM91417;8.5.5: Provide option for backwards compatibility for earexpander
PM91417;8.0.0: Provide option for backwards compatibility for earexpander
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.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
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
APAR status
Closed as program error.
Error description
An option is necessary to provide backwards compatibility for having the EARExpander command line utility extract files from JAR files in all locations, not just in JavaEE active locations.
Local fix
n.a
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Partial application updates will not * * update JARs in non-active Java * * EE locations. * **************************************************************** * RECOMMENDATION: * **************************************************************** Applications deployed to the WebSphere Application Server by default only expand archives in active Java EE locations. For example, JARS in a WAR's WEB-INF/lib directory are active. JARs in other locations within a WAR are not active. Because JARs not in active locations are not expanded, partial application updates are not applied to these JARs. (Whole JAR replacements are applied to these JARs.) For example, the file "SampleScript.js" having the following packaging structure is not updated: SampleEAR.ear/ SampleWAR.war/ WEB-INF/SampleDir/NestedSampleDir/ SampleJar.jar/ SampleScript.js Expansion is performed by internal processing steps, including deployment steps, and including expansions performed by the earExpander script.
Problem conclusion
A custom property has been introduced which enables expansion of all archives, even those outside of active Java EE locations: org.eclipse.jst.j2ee.commonarchivecore.openAllArchives=true By default, the custom property value is false. Setting the value true will revert the fix introduced by PM42643, and set the server to expand all archives. This should be done sparingly since setting the server to expand archives outside of active Java EE locations provides the best performance, and avoids any problems caused by non-valid archives. For example, simple corruption of an archive file, or use of multi-byte characters for entries in a archive file. To enable expansion of non-standard archives during deployment, set the property on the processes involved with the deployment, that is, on the Application Server process, and, if a Deployment Manager is being used, on the Deployment Manager process. To enable expansion by the earExpander script, set the property as a Java Custom property by editing the earExpander script. The property is not applied to JARs within JARs. JARs within JARs will still not be expanded, even with the property set to true. Note that all JARs in EAR files are active and all JARs in RAR files are active. The processing of JARs in EAR files and JARs in RAR files is not affected by the custom property. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.31, 8.0.0.8, and 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
PM91417
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
2013-06-19
Closed date
2013-09-10
Last modified date
2013-09-10
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
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
12 January 2022