IBM Support

PI13683: PARTNER LOG FULL ERROR CWRLS0008E: RECOVERY LOG IS BEING MARKED AS FAILED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the number of Servants is set such that the minimum
    number of servants is set to less than the maximum the
    partner logs may grow until they become full.
    For example:
    BBOM0001I      wlm_maximumSRCount: 8.
    BBOM0001I      wlm_minimumSRCount: 1.
    This occurs when a Servant is stopped and peer recovery
    processing is undertaken for the Servant   Peer recovery
    successfully recovers all the XA resources associated with
    the stopped servant, and this is recorded at the the control
    region.  However, during control region shutdown processing,
    recovery processing interprets the fact that the XA
    resources have recovered as meaning that there is nothing
    required for recovery from the partnerlogs at the next server
    startup, and resets the recovery epoch (a number that defines
    the scope of resources to be recovered) - this causes resource
    references to be left in the partner log, potentially never
    removed.
    
    The following error is seen in the Servant log when the
    log fill full conditon occurs:
    
    Trace: 2013/11/14 07:20:05.289 02 t=9B8B58 c=UNK key=S2 tag=
    (13007004)
    SourceId: com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog
    ExtendedMessage: BBOO0222I: CWRLS0008E: Recovery log is being
    marked as failed. [ 2 transaction ]
    Trace: 2013/11/14 07:20:05.291 02 t=9B8B58 c=UNK key=S2 tag=
    (13007004)
    SourceId: com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog
    ExtendedMessage: BBOO0222I: CWRLS0009E: Details of recovery
    log failure: com.ibm.ws.recoverylog.spi.LogFullException
    at
    com.ibm.ws.recoverylog.spi.MultiScopeRecoveryLog.keypoint(MultiS
    copeRecoveryLog.java:1767)
    at
    com.ibm.ws.recoverylog.spi.LogHandle.getWriteableLogRecord(LogHa
    ndle.java:1248)
    at
    com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.writeSections(Rec
    overableUnitImpl.java:670)
    at
    com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.forceSections(Rec
    overableUnitImpl.java:1047)
    at
    com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.forceSections(Rec
    overableUnitImpl.java:986)
    at
    com.ibm.ws390.recoverylog.spi.ControllerRequestProcessor.driveRe
    coverableUnitMethod(ControllerRequestProcessor.java:358)
    at
    com.ibm.ws390.recoverylog.spi.ControllerRequestProcessor.process
    (ControllerRequestProcessor.java:139)
    

Local fix

  • Set wlm_minimumSRCount=wlm_maximumSRCount
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: XA partner log is marked as failed      *
    *                      due to the recovery log service being   *
    *                      unable to add a partner entry to the    *
    *                      filled log.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    With a specific RACF authorization, a server shutdown will
    reset the RRS Resource Manager token, which includes setting
    the recovery epoch value to zero.  If XA resources had been
    logged to the XA partner log during the lifecycle of the
    server before the shutdown, these resources will not have yet
    been recovered, and will remain in the log until recovery on
    them has been completed.  However, due to the resetting of the
    epoch value, these resources will potentially remain hidden
    from recovery, resulting in the partnerlog gradually filling
    over time, eventually causing the server to fail during server
    startup.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI13683

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-13

  • Closed date

    2014-07-29

  • Last modified date

    2014-08-04

  • 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

  • R800 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":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022