Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
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
The data model and XML serialization layer as present in the IBM WebSphere Application Server provides support for a connection management policy attribute in the IBM web module extended metadata, which is stored as "WEB-INF/ibm-web-ext.xml". However, the schema for the web module extension file does not list the connection management policy attribute. As a result, an attempt to validate an XML format web module extension file that contains an occurrence of the connection management policy attribute incorrectly generates a schema validation error. . IBM Rational Application Developer has a validator for webapps that checks the resource references and the tags in them. If a web-app in WebSphere Application Server V6.1 or previous used the tag connectionManagementPolicy, the tag is migrated to the proper equivalent tag in WebSphere Application Server V7.0, connection-management-policy, . but the Rational Application Developer validation fails. The validator uses the WebSphere AppServer schema file ibm-common-ext_1_0.xsd . Here is an example setting from the WebSphere Application Server V6.1 deployment descriptor file ibm-web-ext.xmi <resourceRefExtensions xmi:id="ResourceRefExtension_1222107474955" isolationLevel="TRANSACTION_READ_COMMITTED" connectionManagementPolicy="Normal"> <resourceRef href="WEB-INF/web.xml#ResourceRef_1222107474923" /> </resourceRefExtensions> . This is migrated to the setting in the ibm-web.xml file <resource-ref name="hamstest" isolation-level="TRANSACTION_READ_COMMITTED" connection-management-policy="NORMAL"/>
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: WEB-INF/ibm-web-ext.xml holding a * * connection management policy fails * * validation if migrated by Rational * * Application Developer * **************************************************************** * RECOMMENDATION: * **************************************************************** The data model and XML serialization layer as present in the IBM WebSphere Application Server provides support for a connection management policy attribute in the IBM Web Module extended metadata. In the IBM WebSphere Application version v6.1 (and earlier), the IBM Web Module extended metadata is stored in the file "WEB-INF/ibm-web-ext.xmi", stored relative to the root location of the Web Module archive. In the IBM WebSphere Application version v7.0 (and later), the IBM Web Module extended metadata is stored in the file "WEB-INF/ibm-web-ext.xml", again stored relative to the root location of the Web Module archive. The schema for the IBM Web Module extended metadata is stored in a file called "ibm-common-ext_1_0.xsd". While the data model provides support for the connection management policy attribute, the schema file (incorrectly) does not. As a result, IBM Web Module extended data, available from an IBM Application Server v6.1 as "WEB-INF/ibm-web-ext.xmi", if containing a connection policy managment value, and if migrated to an IBM Application Server v7.0, and stored as "WEB-INF/ibm-web-ext.xml", results in a file which (incorrectly) does not validate according the IBM Web Module extended data schema. For example, if the v6.1 IBM Web Module extended extended metadata contains the values: <resourceRefExtensions xmi:id="ResourceRefExtension_1222107474955" isolationLevel="TRANSACTION_READ_COMMITTED" connectionManagementPolicy="Normal"> <resourceRef href="WEB-INF/web.xml#ResourceRef_1222107474923"/> </resourceRefExtensions> The v7.0 IBM Web Module extended metadata will contain the values: <resource-ref name="hamstest" isolation-level="TRANSACTION_READ_COMMITTED" connection-management-policy="NORMAL"/>
Problem conclusion
The problem was fixed by updating schema for the IBM Web Module extended metadata to include the missing "connection-management-policy" attribute. That is, the following attribute was added to the schema file: <xsd:attribute name="connection-management-policy"> <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:enumeration value="DEFAULT"/> <xsd:enumeration value="AGGRESSIVE"/> <xsd:enumeration value="NORMAL"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.17. 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
PM25143
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-25
Closed date
2011-03-01
Last modified date
2011-03-01
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
Document Information
Modified date:
24 October 2021