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

Fixes are available

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:
03 May 2022

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?