PI82951: WTRN0100E: Server stopping but no reserved connection when closing SQL RecoveryLog occurs when stopping the server

Fixes are available

APAR status

Closed as program error.

Error description

Shutdown of an application server configured to store
transaction service or compensation service logs in a database
may result in the following error messages:

SQLMultiScope A   WTRN0100E: Server stopping but no reserved
connection when closing SQL RecoveryLog partnerlog for server
CELLNAME\NODENAME\SERVERNAME
SQLMultiScope A   CWRLS0008E: Recovery log is being marked as
failed. [ 2 transaction ]
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:1436)
at
com.ibm.tx.jta.impl.RecoveryManager.postShutdown(RecoveryManager
.java:800)
at
com.ibm.tx.jta.impl.RecoveryManager.resync(RecoveryManager.java:
1716)
at
com.ibm.tx.jta.impl.RecoveryManager.performResync(RecoveryManage
r.java:2286)
at
com.ibm.ws.tx.jta.RecoveryManager.performResync(RecoveryManager.
java:119)
at
com.ibm.tx.jta.impl.RecoveryManager.run(RecoveryManager.java:223
9)
at java.lang.Thread.run(Thread.java:790)
RecoveryManag E   WTRN0029E: Error closing the log in shutdown!

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users that     *
*                  have configured the the transaction or      *
*                  compensation service to store its logs in   *
*                  a database                                  *
****************************************************************
* PROBLEM DESCRIPTION: WTRN0100E: Server stopping but no       *
*                      reserved connection when closing SQL    *
*                      RecoveryLog occurs when stopping the    *
*                      server                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When storing transaction or compensation service logs in a
database, the recovery log component incorrectly used a
single static variable to flag the state of the connections to
the database.  When transactional high availability is used,
or if both the compensation and transaction logs are stored in
a database then this incorrect cardinality may result in the
recovery log component believing that it had lost its
connection to the database resulting in a series of error
messages being issued.  The condition does not compromise
transactional integrity.

Problem conclusion

The recovery log component was modified to track reserved
connection state per recovery log.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.5.5.13 and 9.0.0.5.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PI82951
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-12
Closed date
2017-08-30
Last modified date
2017-08-30

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
WEBS APP SERV N
Fixed component ID
5724H8800

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

PI82951: WTRN0100E: Server stopping but no reserved connection when closing SQL RecoveryLog occurs when stopping the server

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?