com.ibm.websphere.scheduler.TaskInvalid: SCHD0061E: The task information for task ID 4251 and owner token wcm was not found in the database. at com.ibm.ws.scheduler.TaskStoreImpl.load(TaskStoreI mpl.java:950) at com.ibm.ws.scheduler.TaskStoreImpl.findByPrimaryKe y(TaskStoreImpl.java:834) at com.ibm.ws.scheduler.SchedulerImpl$6.run(Scheduler Impl.java:1739) at java.security.AccessController.doPrivileged(Access Controller.java:246) at com.ibm.ws.scheduler.SchedulerImpl.getTask(Schedul erImpl.java:1706) at com.ibm.ws.scheduler.SchedulerImpl.getStatus(Sched ulerImpl.java:1695) at com.ibm.ejs.container.TimerHandleImpl.getTimer(Tim erHandleImpl.java:162) at com.ibm.workplace.wcm.util.scheduler.ejb.EJBSchedu lerBean.execute(EJBSchedulerBean.java:747) at com.ibm.workplace.wcm.util.scheduler.ejb.EJSRemote StatelessEJBScheduler_27162c8e.execute(Unknown Source) at com.ibm.workplace.wcm.util.scheduler.ejb._EJBSched uler_Stub.execute(_EJBScheduler_Stub.java:408) at com.ibm.workplace.wcm.util.scheduler.service.Sched ulerServiceImpl.execute(SchedulerServiceImpl.java: 208) at com.ibm.workplace.wcm.services.task.TaskServiceImp l.startGlobalMonitor(TaskServiceImpl.java:155) at com.ibm.workplace.wcm.services.task.TaskServiceImp l. (TaskServiceImpl.java:126) at com.ibm.workplace.wcm.services.ServiceManager.getT askService(ServiceManager.java:284) at com.ibm.workplace.wcm.services.task.GlobalTaskMoni tor.run(GlobalTaskMonitor.java:64) at com.ibm.wps.services.workmanager.impl.WasWorkWrapp er.run(WasWorkWrapper.java:41) at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2 EEContext.java:261) at java.security.AccessController.doPrivileged(Access Controller.java:219)

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via fixunix.com by Unknown author, 1 year ago
SCHD0061E: The task information for task ID 4251 and owner token wcm was not found in the database. at com.ibm.ws.scheduler.TaskStoreImpl.load(TaskStoreI mpl.java:950) at com.ibm.ws.scheduler.TaskStoreImpl.findByPrimaryKe y(TaskStoreImpl.java:834
com.ibm.websphere.scheduler.TaskInvalid: SCHD0061E: The task information for task ID 4251 and owner token wcm was not found in the database. at com.ibm.ws.scheduler.TaskStoreImpl.load(TaskStoreI mpl.java:950) at com.ibm.ws.scheduler.TaskStoreImpl.findByPrimaryKe y(TaskStoreImpl.java:834) at com.ibm.ws.scheduler.SchedulerImpl$6.run(Scheduler Impl.java:1739) at java.security.AccessController.doPrivileged(Access Controller.java:246) at com.ibm.ws.scheduler.SchedulerImpl.getTask(Schedul erImpl.java:1706) at com.ibm.ws.scheduler.SchedulerImpl.getStatus(Sched ulerImpl.java:1695) at com.ibm.ejs.container.TimerHandleImpl.getTimer(Tim erHandleImpl.java:162) at com.ibm.workplace.wcm.util.scheduler.ejb.EJBSchedu lerBean.execute(EJBSchedulerBean.java:747) at com.ibm.workplace.wcm.util.scheduler.ejb.EJSRemote StatelessEJBScheduler_27162c8e.execute(Unknown Source) at com.ibm.workplace.wcm.util.scheduler.ejb._EJBSched uler_Stub.execute(_EJBScheduler_Stub.java:408) at com.ibm.workplace.wcm.util.scheduler.service.Sched ulerServiceImpl.execute(SchedulerServiceImpl.java: 208) at com.ibm.workplace.wcm.services.task.TaskServiceImp l.startGlobalMonitor(TaskServiceImpl.java:155) at com.ibm.workplace.wcm.services.task.TaskServiceImp l. (TaskServiceImpl.java:126) at com.ibm.workplace.wcm.services.ServiceManager.getT askService(ServiceManager.java:284) at com.ibm.workplace.wcm.services.task.GlobalTaskMoni tor.run(GlobalTaskMonitor.java:64) at com.ibm.wps.services.workmanager.impl.WasWorkWrapp er.run(WasWorkWrapper.java:41) at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2 EEContext.java:261) at java.security.AccessController.doPrivileged(Access Controller.java:219)
at javax.security.auth.Subject.doAs(Subject.java:495)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.