Fixes are available
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
Document Information
Modified date:
27 October 2021