IBM Support

IT26347: JDBC CONNECTION POOL CONTINUES TO RETURN NULL CONNECTION AFTER ORACLE DB CONNECTION LOSS

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

  • When using JDBC connection pooling with an Oracle database, a
    call to
    getJDBCType4Connection() might repeatedly fail with the
    following recoverable exception after a database connection
    outage:
    
    BIP6267E: There has been a problem establishing a connection to
    the JDBC provider ''myJDBCProvider'' in node
    ''myJavaComputeNode''. Exception details:
    'java.sql.Connection=null'
    
    To recover, the integration server has to be restarted.
    
    
    
    Additional Symptom(s) Search Keyword(s):JDBC Connections, null,
    Connection pool,
    

Local fix

  • Disable connection pooling
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10 and IBM App Connect
    Enterprise V11 using JDBC connection pooling with Oracle.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using JDBC connection pooling with an Oracle database, a
    call to getJDBCType4Connection() might repeatedly fail with the
    following recoverable exception after a database connection
    outage:
    
    BIP6267E: There has been a problem establishing a connection to
    the JDBC provider ''myJDBCProvider'' in node
    ''myJavaComputeNode''. Exception details:
    'java.sql.Connection=null'
    
    To recover, the integration server has to be restarted.
    

Problem conclusion

  • The product now recognises some additional Oracle database
    return codes to mean that the JDBC connection is broken.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.15
    v11.0      11.0.0.3
    
    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

    IT26347

  • 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

    2018-09-19

  • Closed date

    2018-12-18

  • Last modified date

    2019-06-20

  • 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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
20 June 2019