PI68664: RECOVERY LOG SERVICE MAY MISCALCULATE FREE SPACE NEEDED FOR KEYPOINT RESULTING IN LOGFULLEXCEPTION

Fixes are available

APAR status

Closed as program error.

Error description

A LogFullException may be thrown due to the miscalculation of
the amount of data needed to be written to the partner logs.
Due to that miscalculation, RLS believes that it needs more
capacity to write records than is actually required.
You may see the following output in the joblogs:
BBOO0220E:
WTRN0000E: An internal error occurred in method logData in clas
s com.ibm.ws.Transaction.JTA.PartnerLogData; the exception
stack trace
follows: com.ibm.ws.recoverylog.spi.LogFullException
at
com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog.keypoint(MultiS
copeReco
veryLog.java:1768)
at
com.ibm.ws.recoverylog.spi.LogHandle.getWriteableLogRecord(LogHa
ndle.jav
a:1248)
at
com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.writeSections(Rec
overable
UnitImpl.java:670)
at
com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.forceSections(Rec
overable
UnitImpl.java:1047)
at
...

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users of JTA   *
*                  Transactions                                *
****************************************************************
* PROBLEM DESCRIPTION: A com.ibm.ws.recoverylog.spi            *
*                      .LogFullException can occur on a        *
*                      keypoint when the logs are not          *
*                      actually full.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The recovery log service removes records by writing a deletion
record.  When the currently active file is full a keypoint
occurs, re-writing the current data, which does not
include deleted records, to the inactive log file which is
then activated.  During keypoint the amount of space required
for the size of the current data is verified as being less than
the file size, if not a LogFullException occurs.
When records are read in during recovery, at server restart,
the recovery log service doesn't decrement the size of records
it has read in when it encounters corresponding deletion
records, leaving the value of the current data's size too
high.
This can result in a LogFullException when the logs are not
actually full.  When such an exception occurs services that use
the recovery log service, such as the transaction service and
the business activity service, will fail.
If the transaction service is configured for high-availability
then the application server will be terminated and recovery
will occur, otherwise the application server will remain
running but subsequent two-phase JTA transactions, which
require use of the recovery log service, will fail.
In cases where the LogFullException does not occur,
performance may be impacted since keypointing will occur more
frequently than necessary.

Problem conclusion

The programming error was fixed so that the recovery log
service correctly adjusts the tracked value for the total size
of the active records when deletion records are encountered
during the recovery process

APAR PI68664 is currently targeted for inclusion in Fix Packs
8.0.0.13, 8.5.5.11 and 9.0.0.2 of WebSphere Application Server.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

In addition, please refer to URL:
http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack PTF information.

Temporary fix

Comments

APAR Information

APAR number
PI68664
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-09-05
Closed date
2016-11-15
Last modified date
2016-11-15

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 FOR Z
Fixed component ID
5655I3500

Applicable component levels

R850 PSY
UP

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

Document Information

Modified date:
03 May 2022

Tips

PI68664: RECOVERY LOG SERVICE MAY MISCALCULATE FREE SPACE NEEDED FOR KEYPOINT RESULTING IN LOGFULLEXCEPTION

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

Document Information

Share your feedback

Need support?