IBM Support

PM20036: FFDC EXCEPTION OCCURRED DURING SERVER STARTUP

Fixes are available

PM20036; 6.1.0.33: ffdc exception occurred during server startup
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During server startup an FFDC occurred with the following
    information:
    
    FFDC Exception:com.ibm.ws.recoverylog.spi.InvalidFailureScopeEx
    ception SourceId:com.ibm.ws.cscope.RecoveryManager.processRecov
    eredData ProbeId:494 Reporter:com.ibm.ws.cscope.RecoveryManager
    @1e501e5
    com.ibm.ws.recoverylog.spi.InvalidFailureScopeException
    at com.ibm.ws.recoverylog.spi.RecoveryDirectorImpl.initialRecov
    eryComplete(RecoveryDirectorImpl.java:1333)
    at com.ibm.ws.cscope.RecoveryManager.processRecoveredData(Recov
    eryManager.java:562)
    at com.ibm.ws.cscope.RecoveryManager.run(RecoveryManager.java:5
    22)
    at java.lang.Thread.run(Thread.java:736)
    
    This occurs when the Compensation Service is enabled and there
    are no CScopes to recover; for example, the first time an
    application server is started with the Compensation Service
    enabled.
    
    There is no functional impact on either CScope recovery or the
    application server startup.  The exception that is written to
    the FFDC can be safely ignored.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All IBM WebSphere Application Server users  *
    *                  of Compensation Service.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: FFDC Exception occurred during server   *
    *                      startup.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During server startup an FFDC occurred with the following
    information:
    
    FFDC Exception:com.ibm.ws.recoverylog.spi.InvalidFailureScopeEx
    ception SourceId:com.ibm.ws.cscope.RecoveryManager.processRecov
    eredData ProbeId:494 Reporter:com.ibm.ws.cscope.RecoveryManager
    @1e501e5
    com.ibm.ws.recoverylog.spi.InvalidFailureScopeException
    at com.ibm.ws.recoverylog.spi.RecoveryDirectorImpl.initialRecov
    eryComplete(RecoveryDirectorImpl.java:1333)
    at com.ibm.ws.cscope.RecoveryManager.processRecoveredData(Recov
    eryManager.java:562)
    at com.ibm.ws.cscope.RecoveryManager.run(RecoveryManager.java:5
    22)
    at java.lang.Thread.run(Thread.java:736)
    
    This occurred when the Compensation Service is enabled and
    there are no CScopes to recover; for example, the first time
    an application server is started with the Compensation
    Service enabled.
    
    The root cause was that method initialRecoveryComplete() was
    being called twice during Compensation service recovery
    processing.
    
    There is no functional impact on either CScope recovery or the
    application server startup.  The exception that is written to
    the FFDC can be safely ignored.
    

Problem conclusion

  • The Compensation Service will be changed to ensure that
    initialRecoveryComplete() is only called once during
    Compensation Service recovery processing.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.35 and 7.0.0.13.  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

    PM20036

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-08-06

  • Closed date

    2010-08-17

  • Last modified date

    2010-09-02

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM20036

Modified date: 02 September 2010