IBM Support

IT41382: BIP2114 ON DEPLOY IF NODE ATTRIBUTES IN THE MSGFLOW OR SUBFLOW FILE APPEAR BEFORE THE XMI:TYPE ATTRIBUTE FOR A NODE

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

  • If properties for a message flow node appear before the node's
    type attribute, and the flow is packaged into a BAR file using
    mqsipackagebar rather than mqsicreatebar, then the message flow
    or subflow may fail to deploy with a BIP2114 error stating ?An
    attempt is being made to modify a locked ConfigObject.?.
    
    For example a .msgflow or .subflow which contains the follow
    node will fail to deploy because the queueName and
    getWithCorrelID properties appear before the xmi:type attribute:
    
    
    <nodes queueName="MY.Q" getWithCorrelID="true"
    xmi:type="ComIbmMQGet.msgnode:FCMComposite_1"
    xmi:id="FCMComposite_1_3" location="434,191" >
       <translation xmi:type="utility:ConstantString" string="MQ
    Get"/>
    </nodes>
    

Local fix

  • Update affected .msgflow or .subflow files to ensure that the
    xmi:type attribute appears first in each  element.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If properties for a message flow node appear before the node's
    type attribute, and the flow is packaged into a BAR file using
    mqsipackagebar rather than mqsicreatebar, then the message flow
    or subflow may fail to deploy with a BIP2114 error stating 'An
    attempt is being made to modify a locked ConfigObject.'
    
    For example a .msgflow or .subflow which contains the following
    node will fail to deploy because the queueName and
    getWithCorrelID properties appear before the xmi:type attribute:
    
    <nodes queueName="MY.Q" getWithCorrelID="true"
    xmi:type="ComIbmMQGet.msgnode:FCMComposite_1"
    xmi:id="FCMComposite_1_3" location="434,191">
       <translation xmi:type="utility:ConstantString"
    string="MQGet"/>
    </nodes>
    

Problem conclusion

  • The product will now correctly deploy nodes in .msgflow or
    .subflow files when the xmi:type attribute is not the first
    attribute listed on a <nodes> element.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.20
    v12.0      12.0.7.0
    
    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

    IT41382

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-06-29

  • Closed date

    2022-10-26

  • Last modified date

    2022-10-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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2022