IBM Support

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

Fixes are available

9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
16.0.0.4: WebSphere Application Server Liberty 16.0.0.4
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
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
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
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
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.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
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

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

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":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021