IBM Support

IT09526: TWO DIFFERENT JDBC CONNECTIONS WITH JDBCPROVIDERXASUPPORT WITH DIFFERENT VALUES USED IN SAME FLOW CAUSE CONNECTION ERROR

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 two different JDBC configurable services with different
    jdbcProviderXASupport property values are used within a single
    message flow, a continuous connection error is observed:
    
    com.ibm.broker.jdbctype4.localtrxn.JDBCType4SinglePhaseTrxnHandl
    erErrors
    @320421dc.JDBCType4SinglePhaseTrxnhandlerErrors::throwException'
    parms','methodName=JDBCType4SinglePhaseTrxnTable::addTrxnBranch
    msgKey=6268 action=1 reason=Broken Connection found at
    transaction start for new trxn branch length of inserts =2'
    JDBCType4SinglePhaseTrxnTable.addTrxnBranch '( JDBC PROVIDER )
    Return from XAResource start() rCode =-5'
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker V8.0 and IBM Integration
    Bus V9.0 and V10.0 who use JDBC configurable services.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When two different JDBC configurable services are defined with
    different jdbcProviderXASupport property values and JDBC
    connections for both the configurable services are obtained
    within a single message flow, a continuous connection error is
    observed.
    
    <i>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</i>
    

Problem conclusion

  • Errors are no longer observed when connections with different
    jdbcProviderXASupport values are obtained in a single message
    flow.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.8
    v9.0       9.0.0.6
    v10.0      10.0.0.2
    
    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

    IT09526

  • 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

    2015-06-18

  • Closed date

    2015-09-10

  • Last modified date

    2016-04-21

  • 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