IBM Support

PI72179: TRANSACTION LOGGING TO RDBMS REFINEMENT FOR JDBC4.1 COMPLIANCE

Fixes are available

9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When WebSphere Application Server is configured to store
    transaction logs in an Oracle v12 database, the starting and
    stopping of the WAS server leads to the reporting of errors
    related to JDBC4.1 compliance.
    
    At startup :
    DSRA8230W: The application server is unable to determine if a
    transaction should be resolved because data source custom
    property nonTransactionalDataSource is configured but data
    source custom property commitOrRollbackOnCleanup is not
    configured.
    
    At shutdown :
    [09/11/16 10:21:25:379 GMT] 00000048 SQLMultiScope A
    WTRN0100E: Server stopping but no reserved connection when
    closing SQL RecoveryLog partnerlog for server
    CellCell01\NodeNode01\server1
    [09/11/16 10:21:25:395 GMT] 00000048 SQLMultiScope A
    CWRLS0008E: Recovery log is being marked as failed. [ 2
    transaction ]
    [09/11/16 10:21:25:396 GMT] 00000048 SQLMultiScope I
    CWRLS0009E: Details of recovery log failure: Server stopping,
    no reserved connection,
    com.ibm.ws.recoverylog.spi.InternalLogException: Server
    stopping, no reserved connection
     at
    com.ibm.ws.recoverylog.custom.jdbc.impl.SQLMultiScopeRecoveryLog
    .closeLog(SQLMultiScopeRecoveryLog.java:1419)
     at
    com.ibm.tx.jta.impl.RecoveryManager.postShutdown(RecoveryManager
    .java:799)
     at
    com.ibm.ws.tx.jta.FailureScopeController.shutdown(FailureScopeCo
    ntroller.java:344)
     at
    com.ibm.ws.runtime.component.TxServiceImpl.destroy(TxServiceImpl
    .java:1220)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server utilising transaction logging to     *
    *                  database                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When WebSphere Application Server is    *
    *                      configured to store transaction logs    *
    *                      in an Oracle v12 database, starting     *
    *                      and stopping the server leads to        *
    *                      JDBC4.1 compliance error reports.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Oracle v12 driver provides full JDBC 4.1 compliance.
    This has resulted in changes of behaviour when compared to
    earlier (pre-v12) versions of the driver.
    

Problem conclusion

  • Changes were implemented to the connection handling when
    using Oracle v12 database driver, to maintain consistent
    behaviour between Oracle driver releases.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.12 and 9.0.0.4.  Please refer to the
    Recommended Updatespage for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI72179

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-14

  • Closed date

    2017-06-06

  • Last modified date

    2017-06-06

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 December 2021