A fix is available
APAR status
Closed as program error.
Error description
When WebSphere is configured to use a custom scheduler for use by the EJB Timer Service, the Timer Bean fails to start resulting in the FFDC file and stacktrace: FFDC Exception:java.lang.IllegalArgumentException SourceId:com.ibm.ws.scheduler.TaskStoreImpl.loadTasksFromResultS et ProbeId:650 Reporter:com.ibm.ws.scheduler.TaskStoreImplDB2@77ac77ac java.lang.IllegalArgumentException: Task Id Not Registered com.ibm.ws.scheduler.SchedulerServiceImpl.getTaskInfoImplementat ion com.ibm.ws.scheduler.TaskStoreImpl.loadTaskFromResultSet com.ibm.ws.scheduler.TaskStoreImpl.loadTasksFromResultSet com.ibm.ws.scheduler.SchedulerDaemonImpl.poll com.ibm.ws.scheduler.SchedulerDaemonImpl.run com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run java.security.AccessController.doPrivileged com.ibm.ws.asynchbeans.J2EEContext.run com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go com.ibm.ws.asynchbeans.ABWorkItemImpl.run com.ibm.ws.asynchbeans.WLMABWorkItemImpl.run java.lang.Thread.run
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1.0 that use a custom scheduler * * configuration for the EJB Timer Service. * **************************************************************** * PROBLEM DESCRIPTION: When the EJB Timer Service is * * configured to use a custom scheduler, * * the EJB Timer Service may not start. * **************************************************************** * RECOMMENDATION: * **************************************************************** When starting an application containing EJB 3.0 beans and the EJB Timer Service has been configured to use a custom scheduler, the EJB Timer Service may not start resulting in the following FFDC file and stacktrace: FFDC Exception:java.lang.IllegalArgumentException SourceId:com.ibm.ws.scheduler.TaskStoreImpl.loadTasksFromResultS et ProbeId:650 Reporter:com.ibm.ws.scheduler.TaskStoreImplDB2@77ac77ac java.lang.IllegalArgumentException: Task Id Not Registered com.ibm.ws.scheduler.SchedulerServiceImpl.getTaskInfoImplementat ion com.ibm.ws.scheduler.TaskStoreImpl.loadTaskFromResultSet com.ibm.ws.scheduler.TaskStoreImpl.loadTasksFromResultSet com.ibm.ws.scheduler.SchedulerDaemonImpl.poll com.ibm.ws.scheduler.SchedulerDaemonImpl.run com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run java.security.AccessController.doPrivileged com.ibm.ws.asynchbeans.J2EEContext.run com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go com.ibm.ws.asynchbeans.ABWorkItemImpl.run com.ibm.ws.asynchbeans.WLMABWorkItemImpl.run java.lang.Thread.run
Problem conclusion
When the EJB Timer Service has been configured to use a custom scheduler, the EJB Timer Service will always be started. APAR PM64957 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.45 of WebSphere Application Server V6.1. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM64957
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-18
Closed date
2012-05-31
Last modified date
2012-10-01
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
R610 PSY UK81646
UP12/09/23 P F209
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022