IBM Support

IT30813: UNDEPLOYING A MESSAGE SET IN AN INDEPENDENT STATIC LIBRARY CAN TRIGGER ABENDS IF USED BY AN INDEPENDENT MESSAGE FLOW

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • It is possible to deploy the same message set to an integration
    server multiple times if they are put in differently named
    static libraries and are only consumed by an independent
    message flow. In this case abends during message processing or
    on integration server shutdown can occur if one of these static
    libraries is undeployed.
    

Local fix

  • Do not deploy two static libraries which both provide the same
    message set to the same integration server
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus v10 who deploy MRM message sets
    in static libraries as independent resources which are used by
    message flows which are also deployed as independent resources.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If an MRM message set is deployed to an Integration Server as an
    independent resource in a static library, and is then used by a
    message flow also deployed as an independent resource which is
    not in the same static library, then attempting to use the MRM
    parser again in the message flow after undeploying the static
    library will trigger an abend. An abend will also be triggered
    if the flow is stopped or undeployed in a separate configuration
    action after undeploying the static library. This is caused by
    the MRM parser maintaining references to memory owned and freed
    by the message set.
    
    The abend stack will contain entries similar to the
    following:<p>
    #5  0x7f566e98d751 in ImbSemaphoreBase::Semaphore::lock() from
    /appl/IBM/iib/iib-10.0.0.14/server/lib/libCommonServices.so</p><
    p>#6  0x7f566e98d88d in
    ImbSemaphoreBase::Semaphore::Semaphore(ImbSemaphoreBase&,
    ImbSemaphoreBase::Semaphore::State) from
    /appl/IBM/iib/iib-10.0.0.14/server/lib/libCommonServices.so</p><
    p>#7  0x7f55d40bedac in
    CpContext::releaseWorkerAndDictionary(CpContext::Operation,
    bool, bool) from
    /appl/IBM/iib/iib-10.0.0.14/server/lil/MtiImbParser.lil</p><p>#8
      0x7f55d40beeca in CpContext::&#126;CpContext() from
    /appl/IBM/iib/iib-10.0.0.14/server/lil/MtiImbParser.lil</p>
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT30813

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-10-31

  • Closed date

    2020-06-10

  • Last modified date

    2020-06-10

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 June 2020