Fixes are available
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
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.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
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
Deployment of an application containing a 2.4 version webmodule fails with the message : SystemErr R com.ibm.websphere.management.application.client.AppDeploymentExc eption: ADMA0207E: EE 5 module AddSACAddressWeb.war in ear file contains unsupported xmi format bindings file. . This error occurs when the deployment descriptor for a 2.4 version webmodule contains a !DOCTYPE statement.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0, V8.0, and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: J2EE 1.4 applications and modules * * which contain a !DOCTYPE statement in * * their deployment descriptor may be * * versioned 1.5 * **************************************************************** * RECOMMENDATION: * **************************************************************** The deployment descriptor parsing function for an enterprise application or module sets the application/module J2EE version based on the SYSTEM attribute of a !DOCTYPE statement or the schema and version attributes in the root element. The !DOCTYPE statement is used for J2EE 1.3 and earlier applications and modules. For J2EE 1.4 and higher the version is specified by the schema and version attributes. When loading the deployment descriptor, the !DOCTYPE statement is processed after parsing the version attribute. If the deployment descriptor for a J2EE 1.4 application or module contains a !DOCTYPE statement and the SYSTEM attribute is absent, or does not match a known version value, the application or module version will be set to a default value. The default value is the highest version understood by the IBM WebSphere Application Server. That can result in a module being incorrectly interpreted to be a higher version than is recorded in the descriptor and lead to errors during deployment. In this specific instance, a 2.4 version web module had it's version set to 2.5. This caused the deployment to fail due to the presence of XMI based bindings/extensions files in the module. These would be valid for a 2.4 version module but are not allowed for 2.5 and higher version modules.
Problem conclusion
The parsing function has been changed to not set a default value for the version if a !DOCTYPE statement with an unrecognized or null SYSTEM attribute exists. APAR PM67046 is currently targeted for inclusion in Fix Packs 7.0.0.27, 8.0.0.6, and 8.5.0.1 of WebSphere Application Server. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM67046
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-06-18
Closed date
2012-09-13
Last modified date
2013-02-04
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 FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK90578
UP13/01/18 P F301
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
29 October 2021