JR46631: MQ BINDING FAILED TO GET JNDI AFTER SET COM.IBM.BPM.FDS.SCA.DEPLOY.OUTOFPROCESS PROPERTY TO TRUE

Download Version 8.0.1 Fix Pack 2 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 1 for the IBM Business Process Manager products
Version 7.5.1 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as fixed if next.

Error description

• After set the property com.ibm.bpm.fds.sca.deploy.outOfProcess
  to
  true will made the deploy process take a new path to deploy the
  application to the server. But this brings a issue which made
  some
  context haven't been initialized successfully. Which made the
  bindings
  which need to create some resources in server failed. And it
  will thrown
  some exception when the process run like below:
      javax.naming.NameNotFoundException:
  Name comp/env/sca not found in context "java:".
  at
  com.ibm.ws.naming.ipbase.NameSpace.getParentCtxInternal(NameSpac
  e.java:1
  837)
   at
  com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java
  :1166)
  at
  com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:1095)
  at
      This APAR will correct this issue.
  

Local fix

• 1. Setting the property com.ibm.bpm.fds.sca.deploy.outOfProcess
  to false
  2. Installing the EAR file via the administrative console
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Business Process Manager Advanced users     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Process deploy may fail with            *
  *                      NameNotFound exception when the         *
  *                      com.ibm.fds.sca.deploy.outOfProcess     *
  *                      property is enabled.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When enabling the com.ibm.fds.sca.deploy.outOfProcess
  property, the deploy process will be invoked by another thread
  than the invoking one as the context may not initialized
  correctly.
  The fix will be provided in upcoming releases.
  

Problem conclusion

Temporary fix

Comments

• The fix will be provided in upcoming releases.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R750 PSY

     UP

• R800 PSY

     UP