IBM Support

PM46159: FINDEJBTIMERS AND CANCELEJBTIMERS COMMANDS DO NOT WORK

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The target server will have an FFDC incident report with the
    following exception stack trace:
    com.ibm.ws.scheduler.exception.SchedulerServiceNotInitialized:
    SCHD0126E: The scheduler service singleton has not been set.
    at com.ibm.ws.scheduler.SchedulerServiceImpl.instance(
    SchedulerServiceImpl.java:201)
    at com.ibm.ws.scheduler.TaskInfoBinaryData.getJ2EEName(
    TaskInfoBinaryData.java:514)
    at com.ibm.ws.scheduler.TaskInfoBinaryData.getTargetRunnable(
    TaskInfoBinaryData.java:562)
    at com.ibm.ejs.container.TimerTaskInfoImpl.getHandler(
    TimerTaskInfoImpl.java:677)
    at com.ibm.ejs.container.TimerTaskInfoImpl.getParsedSchedule(
    TimerTaskInfoImpl.java:858)
    at com.ibm.ejs.container.TimerTaskInfoImpl.writeObject(
    TimerTaskInfoImpl.java:743)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server V8.0 users of  *
    *                  EJB timers                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: The findEJBTimers and cancelEJBTimers   *
    *                      commands do not work on z/OS.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The findEJBTimers and cancelEJBTimers commands use MBean
    operations to communicate with the server.  On z/OS, the the
    MBean operation is forwarded from the control region to the
    servant region, the timer info objects are serialized in the
    servant region, deserialized in the control region,
    re-serialized in the control region, and deserialized by the
    commands.  While re-serializing in the control region, the
    timer info object attempts to reconstitute data by accessing
    the scheduler service, which fails because the scheduler
    service does not start in the control region.
    

Problem conclusion

  • The timer info objects have been updated to directly
    re-serialize the deserialized data in the control region rather
    than attempting to reconstitute it.
    
    APAR PM46159 is currently targeted for inclusion in
    Service Level (Fix Pack) 8.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
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM46159

  • 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

    2011-08-22

  • Closed date

    2011-09-07

  • Last modified date

    2012-08-09

  • 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:
27 October 2021