PM63544: JAVA.LANG.ILLEGALARGUMENTEXCEPTION: TASK ID NOT REGISTERED WHEN USING EJB TIMER SERVICE

Fixes are 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 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 PM63544 is currently targeted for inclusion in
WebSphere Application Server Fix Packs 7.0.0.25, 8.0.0.4, and
8.5.0.1.

Sysroute APAR PM64957 will be used to deliver this fix in
WebSphere Application Server V6.1 Fix Pack 6.1.0.45.

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
PM63544
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-04-30
Closed date
2012-05-18
Last modified date
2012-11-02

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PM64957

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK81738
UP12/10/04 P F210

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM63544: JAVA.LANG.ILLEGALARGUMENTEXCEPTION: TASK ID NOT REGISTERED WHEN USING EJB TIMER SERVICE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY UK81738

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.

Document Information

Share your feedback

Need support?