IBM Support

PI11184: ABENDS DURING JAVACOMPUTE NODE PREPARE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abends may be seen when preparing a JavaCompue node during
    startup,
    deploy, flow start or when running some mqsi commands.
    The abend stack may look like the following:
    
      RUNCALLINMETHOD
                  -00022B48 *PATHNAM Exception
      gpProtectedRunCallInMethod
                  +0000003E *PATHNAM j201208 Call
      signalProtectAndRunGlue
                  +0000001C *PATHNAM j201208 Call
      j9sig_protect
                  +0000071A *PATHNAM j201208 Call
      gpCheckCallin
                  +000000A4 *PATHNAM j201208 Call
      callVirtualVoidMethodV
                  +00000060 *PATHNAM j201208 Call
      JNIEnv_::CallVoidMethod(_jobject*,_jmethodID*,...)
                  +00000040 *PATHNAM FP05... Call
      ImbJniNode::prepare()
                  +000003CA *PATHNAM FP05... Call
      ImbDataFlowManager::prepare()
                  +0000026A *PATHNAM FP05... Call
      ImbDataFlowDirector::prepare()
                  +000008F6 *PATHNAM FP05... Call
      ImbConfigurationNode::Transaction::commit()
                  +0000009C *PATHNAM FP05... Call
      ImbConfigurationNode::evaluate(const ImbMessageAssembly&,con
                  +0000339C *PATHNAM FP05... Call
    
    
    and examination of the Java stack at the time of the abend
    will show:
    
    com/ibm/broker/javacompute/MbRuntimeJavaComputeNode.onInitialize
    Delegate
    com/ibm/broker/javacompute/MbRuntimeJavaComputeNode.prepare
    
    The mqsicommands which may cause the problem are:
     . mqsichangetrace with the -f messageFlow flag.
     . mqsireportproperties with the -o ExecutionGroup -r flags.
     . mqsichange/report flowmonitoring with the -f or -j flags.
     . mqsichange/report flowuserexits with the -f flag.
     . mqsistartmessage flow
    
    For the 'report' commands to cause the problem there has to be a
    stopped flow in the execution group. The 'change' commands can
    cause the
    problem even if there is not a stopped flow.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker V7.0 & V8.0.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    Abends may be seen when preparing a JavaCompue node during
    startup, deploy, flow start or when running some mqsi commands.
    During the creation of a JavaCompute node the product is not
    correctly moving a Java object from one LocalFrame to another
    and so ends up referencing a freed object, which can lead to
    an abend.
    
    
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0. For
    details visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • The product now correctly pops the Java object from one
    LocalFrame into another and keeps a reference to a valid object.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.0.7
    v8.0       8.0.0.5
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available, information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI11184

  • Reported component name

    WEB MB Z/OS

  • Reported component ID

    5655V6000

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-06

  • Closed date

    2014-02-26

  • Last modified date

    2014-02-26

  • 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

    WEB MB Z/OS

  • Fixed component ID

    5655V6000

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
26 February 2014