IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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 number

    JR46631

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-13

  • Closed date

    2013-06-27

  • Last modified date

    2013-06-27

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
27 June 2013