IBM Support

PM73223: FFDC LOGS MAY BE GENERATED FOR EJB TIMER FUNCTIONS EVEN THOUGH THEY ARE PERFORMING NORMALLY.

Fixes are available

7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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

  • FFDC LOG GENERATED Exception:
    **********************
    Exception:com.ibm.websphere.scheduler.TaskInvalid
    SourceId:com.ibm.ejs.container.TimerImpl.checkTimer ProbeId:968
    Reporter:com.ibm.ejs.container.TimerImpl@782d6e3
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server with applications that use EJB       *
    *                  timers.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: FFDC logs may be generated for EJB      *
    *                      timer functions even though they are    *
    *                      performing normally.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an application attempts to access an EJB timer that has
    been removed, the application will receive a
    NoSuchObjectLocalException. This is normal and would be
    handled by the application. However, even though the
    application will perform normally, an FFDC log will also be
    generated.  An exception stack in the FFDC log will look
    like this:
    Exception:com.ibm.websphere.scheduler.TaskInvalid
    SourceId:com.ibm.ejs.container.TimerImpl.checkTimer ProbeId:968
    Reporter:com.ibm.ejs.container.TimerImpl@782d6e3
    com.ibm.websphere.scheduler.TaskInvalid: SCHD0061E: The task
    information
    for task ID 556 and owner token wcm was not found in the
    database.
    at
    com.ibm.ws.scheduler.TaskStoreImpl.load(TaskStoreImpl.java:1158)
    at
    com.ibm.ws.scheduler.TaskStoreImpl.findByPrimaryKey(TaskStoreImp
    l.java:1042)
    at
    com.ibm.ws.scheduler.SchedulerImpl$7.run(SchedulerImpl.java:2174
    )
    at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:254)
    at
    com.ibm.ws.scheduler.SchedulerImpl.getTask(SchedulerImpl.java:21
    41)
    at
    com.ibm.ws.scheduler.SchedulerImpl.getStatus(SchedulerImpl.java:
    2130)
    at
    com.ibm.ejs.container.TimerImpl.getTaskStatus(TimerImpl.java:510
    )
    at
    com.ibm.ejs.container.TimerImpl.checkTimer(TimerImpl.java:1173)
    at
    com.ibm.ejs.container.TimerImpl.getHandle(TimerImpl.java:760)
    

Problem conclusion

  • An FFDC log will no longer be produced when an application
    attempts to access an EJB timer that has been removed.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.27, 8.0.0.6, 8.5.0.2.  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

    PM73223

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-19

  • Closed date

    2012-09-25

  • Last modified date

    2012-11-27

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 8.0

Reference #: PM73223

Modified date: 27 November 2012