Fixes are available
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
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
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
The following error is encountered using EJBDeploy when an EJB module is set to metadata-complete=true during deployment. [3/1/17 4:55:08:441 UTC] 000001fb DeployEJBTask I ADMA0158I: [EJBDeploy] Error executing deployment: org.eclipse.emf.common.util.WrappedException. Error is org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'interceptors'. One of '{"http://java.sun.com/xml/ns/javaee":ejb-client-jar}' is expected.. [3/1/17 4:55:08:442 UTC] 000001fb DeployEJBTask I ADMA0158I: [EJBDeploy] org.eclipse.emf.common.util.WrappedException: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'interceptors'. One of '{"http://java.sun.com/xml/ns/javaee":ejb-client-jar}' is expected.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server who set EJB modules to * * metadata-complete during deployment and * * use the EJBDeploy tool. * **************************************************************** * PROBLEM DESCRIPTION: Setting an EJB Module to * * metadata-complete during deployment * * might cause the creation of an * * invalid ejb-jar.xml * **************************************************************** * RECOMMENDATION: * **************************************************************** If you set metadata-complete for an EJB module during deployment using the administrative console, an ejb-jar.xml file is generated that might be invalid. An invalid descriptor is created when either of the elements <module-name> or <interceptors> exists or is generated in the descriptor. The generated descriptor is invalid because those elements are written in the wrong order. This problem cannot be avoided by placing a properly ordered EJB descriptor in the application which is to be deployed, nor by re-ordering the elements of an EJB descriptor already present in the application which is to be deployed. The code which writes the descriptor orders the elements of the descriptor according to rules embedded in the code; the code does not use the order of the elements as they originally appear in the descriptor. Normally, the invalid EJB descriptor does not cause a problem. The application is deployed and can be used by the application server. A problem occurs if EJBDeploy is run during deployment. EJBDeploy performs validation on the EJB descriptor, which detects the invalid element ordering, and which causes the deployment to fail. When the problem occurs, messages similar to the following will be seen in the SystemOut.log file: [3/1/17 4:55:08:441 UTC] 000001fb DeployEJBTask I ADMA0158I: [EJBDeploy] Error executing deployment: org.eclipse.emf.common.util.WrappedException. Error is org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'interceptors'. One of '{"http://java.sun.com/xml/ns/javaee":ejb-client-jar}' is expected.. [3/1/17 4:55:08:442 UTC] 000001fb DeployEJBTask I ADMA0158I: [EJBDeploy] org.eclipse.emf.common.util.WrappedException: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'interceptors'. One of '{"http://java.sun.com/xml/ns/javaee":ejb-client-jar}' is expected.
Problem conclusion
The code was updated to generate the elements in the proper order when the ejb-jar.xml file is written. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.13 and 9.0.0.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
PI78526
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-03-20
Closed date
2017-06-05
Last modified date
2017-06-05
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
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022