PI29967: MIXED NODE DEPLOYMENT FAILS WHEN APPLICATION EJB UPGRADED BY THE APPLICATION SERVER

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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.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
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• During deployment of an application into a mixed node cell,
  WebSphere Application Server is upgrading the EJB version
  of the application.  This causes the deployment of the
  application to fail when it is deployed from a Deployment
  Manager to a node running a version of WebSphere Application
  Server that implements a lower EJB specification level.
  
  The following error surfaces in the servant region SYSPRINT:
  
  Trace: 2014/11/03 03:45:36.761 02 t=AAB988 c=UNK key=P8 tag=
  (13007004)
     SourceId:
  com.ibm.ws.management.application.InstallSchedulerImpl
  ExtendedMessage: BBOO0222I: ADMA5016I: Installation of
  EAR_File_Name started.
  com.ibm.websphere.management.exception.AdminException:
  ADMA5055E:  Errors in validating application target association
  for EAR_File_Name  ADMA0251E: [JAR] module version [3.1] is not
  supported on version [7] nodes [node_name]
  
  Prior to migrating to a mixed node cell, the annotation would
  have been ignored when the deployed into the WebSphere
  Application Server that implements only the lower EJB
  specification level.
  

Local fix

• Remove EJB 3.1 annotation
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: When deploying an application           *
  *                      containing Java EE 1.6 field or method  *
  *                      annotations from a version 8 or         *
  *                      higher Deployment Manager to a version  *
  *                      7 node, the deployment fails.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When deploying an application from a WebSphere Application
  Server version 8 or higher deployment manager to a node running
  WebSphere Application Server version 7, the
  "org.eclipse.jst.j2ee.commonarchivecore.ignore.jee6.annotation=t
  rue"
  custom property can be used to prevent the processing of Java
  EE 1.6 annotations.  Without this property, the WebSphere
  Application Server version 8 deployment manager processes the
  Java EE 1.6 annotations causing the version of the application
  to be upgraded and the deploy to fail on version 7 nodes.
  With the custom property set, Java EE 1.6 class annotations
  are correctly filtered, however method and field annotations
  are not.  In a mixed cell environment, an application that
  contains Java EE 1.6 method or field annotations can fail to
  deploy even though the
  "org.eclipse.jst.j2ee.commonarchivecore.ignore.jee6.annotation=t
  rue"
  custom property is set.
  The resulting error message looks like the following:
  ADMA0251E: [JAR] module version [3.1] is not supported on
  version [7] nodes [wdnodev]
  

Problem conclusion

• This APAR ensures that all Java EE 1.6 annotations are ignored
  when the
  "org.eclipse.jst.j2ee.commonarchivecore.ignore.jee6.annotation=t
  rue" custom property is set, including method and field
  annotations.  This enables the deployment of applications with
  Java EE 1.6 annotations in mixed cells containing target nodes
  that don't support Java EE 1.6.
  
  After the APAR is applied, redeploy the application with
  the
  "org.eclipse.jst.j2ee.commonarchivecore.ignore.jee6.annotation=t
  rue"
  custom property set.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.6. Please refer to the recommended updates page
  for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  In addition, please refer to URL:
  http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack PTF information.
  

Temporary fix

Comments

APAR Information

• 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

• R850 PSY

     UP