PM58817: DEPLOYMENT MANAGER MIGRATION TO V8 FAILS DURING RE-INSTALLATION OF APPLICATIONS WITH EJB JAR MODULES VERSIONED AT 3.0.

8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• EJB Jar 3.0 modules previously deployed to v7 nodes are
  errornesouly identified as 3.1 during migration and prevented
  from installing on v7 nodes.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server migrating a V7.0 Deployment          *
  *                  Manager profile to V8.0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Deployment Manager migration fails      *
  *                      to re-install applications with EJB     *
  *                      3.0 modules.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Deployment Manager migration from V7.0 to V8.0 fails when
  re-installing applications with EJB 3.0 modules.
  The following error may be seen:
  [02/14/2012 17:03:44:610 CST]
  com.ibm.websphere.management.exception.AdminException:
  ADMA5055E: Errors in validating application target association
  for IBM_BPM_WebAPI_MyPC.AppTarget -
  [02/14/2012 17:03:44:610 CST] ADMA0110E:  This type of J2EE
  application 50 is not supported on nodes [BPMJumbo31Node01,
  BPMJumbo31Node02] of version [7, 7]
  [02/14/2012 17:03:44:610 CST]     at
  com.ibm.ws.management.application.task.ValidateAppTask.performTa
  sk(ValidateAppTask.java:374)
  [02/14/2012 17:03:44:610 CST]     at
  com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImp
  l.java:315)
  [02/14/2012 17:03:44:610 CST]     at
  java.lang.Thread.run(Thread.java:769)
  An application with one or more EJB 3.0 modules may be
  incorrectly identified as supporting EJB 3.1. This is caused
  when annotations processing erroneously adds the <local-bean/>
  element onto a Session Bean in the EJB module. Because only
  V8.0 nodes support the EJB 3.1 specification, re-installation
  of that application is prevented for the original V7.0
  nodes.
  

Problem conclusion

• A fix in the annotations processing component has been made to
  properly set the <local-bean/> element only when required by
  the EJB 3.1 specification.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.3.  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 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

• R800 PSY

     UP