IBM Support

IT15258: MESSAGE FLOW USING JDBC XA COORDINATION FAILS AT START UP.

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

  • A message flow that obtains a JDBC Connection using the MbNode
    getJDBCType4Connection() API is configured for (XA) global
    coordination of JDBC operations but fails with the following
    message in the system log:
    
        BIP2374W: Problem configuring XA Coordination for JDBC.
                              could not store Execution Group
    Listener Port.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users IBM Integration Bus v9 & v10 using global coordination
    of JDBC work performed on a managed JDBC connection  which is
    obtained using the MbNode.getJDBCTypeConnection() API in a
    JavaCompute node.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A message flow that obtains a JDBC Connection using the MbNode
    getJDBCType4Connection() API is configured for (XA) global
    coordination of JDBC operations but fails with the following
    message in the system log:
    
        BIP2374W: Problem configuring XA Coordination for JDBC.
                              could not store Execution Group
    Listener Port.
    
    
    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 no longer fails at start up of an Integration Server
    that is configured for global coordination of work performed on
    an IBM Integration Bus managed JDBC Connection.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.6
    v9.0       9.0.0.6
    
    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

    IT15258

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-12

  • Closed date

    2016-09-02

  • Last modified date

    2016-09-02

  • 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

    5724J0530

Applicable component levels

  • R900 PSY

       UP

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

Document Information

Modified date:
23 March 2020