JR51590: DUPLICATE JNDI BINDINGS ARE CREATED WHEN YOU IMPORT AN EAR FILE, PREVENTING THE APPLICATION FROM STARTING

8.5.0.2-WS-BPM-IFJR51590

APAR status

• Closed as program error.

Error description

• When you install the EAR that was created in IBM Integration
  Developer, export the application EAR file from IBM Process
  Server, and then reinstall a new version EAR file of the same
  application, the JNDI bindings that the application uses are
  recreated twice. This duplication prevents the application
  from starting.
  
  If you encounter this error, you might see the following
  errors in your SystemOut.log file::
  
  [9/23/14 16:38:15:723 GMT+07:00] 00000068 ModuleDataObj E
  CWMDF0001E: Component ........ already exists.
  [9/23/14 16:38:15:724 GMT+07:00] 00000068 EJBContainerI E
  WSVR0039E: Unable to start EJB jar, <<jar name>>: Component
  already exists:  J2EEName =  .................
  [9/23/14 16:38:15:724 GMT+07:00] 00000068 DeployedAppli W
  WSVR0206E: Module, <<jar name>>, of application,
  <<application name>>, failed to start
  

Local fix

• If available, the original WID EAR can be imported instead
  of the exported EAR from BPM WPS
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM Business Process Manager (BPM)          *
  *                  Advanced                                    *
  *                  IBM BPM Advanced: Process Server            *
  *                  IBM BPM Standard                            *
  *                  IBM BPM Express                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: When you install the EAR that was       *
  *                      created in IBM Integration Developer,   *
  *                      export the application EAR file from    *
  *                      IBM Process Server,and then reinstall   *
  *                      a new version EAR file of the same      *
  *                      application, the JNDI bindings that     *
  *                      the application uses are recreated      *
  *                      twice. This duplication prevents the    *
  *                      application from starting.              *
  *                      If you encounter this error, you        *
  *                      might see the following errors in       *
  *                      your SystemOut.log file:                *
  *                      [9/23/14 16:38:15:723 GMT+07:00]        *
  *                      00000068 ModuleDataObj E CWMDF0001E:    *
  *                      Component ........ already exists.      *
  *                      [9/23/14 16:38:15:724 GMT+07:00]        *
  *                      00000068 EJBContainerI E WSVR0039E:     *
  *                      Unable to start EJB jar, <<jar          *
  *                      name>>: Component already exists:       *
  *                      J2EEName =  .................           *
  *                      [9/23/14 16:38:15:724 GMT+07:00]        *
  *                      00000068 DeployedAppli W WSVR0206E:     *
  *                      Module, <<jar name>>, of application,   *
  *                      <<application name>>, failed to start   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an EAR file is created in IBM Integration Developer and
  imported into Process Server, the server creates some JNDI
  bindings. When you export the application EAR file from
  Process Server and uninstall it, these JNDI binding should be
  also uninstalled. After you reinstall a new version EAR file
  of the same application, the JNDI bindings are re-created.
  However, the JNDI bindings are not uninstalled correctly in
  some cases and cause duplication. The enterprise application
  will not start because of the JNDI duplication.
  

Problem conclusion

• A fix is available for IBM BPM V8.0.1.2 that prevents the JNDI
  bindings from being created twice. Without the duplication,
  the enterprise application starts successfully after the EAR
  file is reinstalled.
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR51590:
      1.  Select IBM Business Process Manager with your edition
  from the product selector, the installed version to the fix
  pack level, and your platform; and then click Continue.
      2.  Select APAR or SPR, enter JR51590, and click Continue.
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  

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

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R800 PSY

     UP