Skip to Content
avatar image
Former Member

After update to BPA: System-Processes don't reschedule (JCS-102016)

Hi Guys,

after having successfully updated one of our Scheduler instances to V9, we did another update today on our Test-Machine.

For currently four "System"-processes, we get the following Error (in two OP-Messages):

1.

Rescheduling of new process for recurrence failed for process System_ProcessKeepClauses with latest process 6,213,248. The queue that it must be submitted to does not have a resource that is required to run it; fix this first. If already fixed, do you want to retry?

2.

Work failed because of exception when rescheduling job group for job 126338318
JCS-102016: Cannot prepare non-current copy of process definition: Process Definition System_ProcessKeepClauses (Copy from 2009/09/24 16:43:51,357 MET)
  at com.redwood.scheduler.model.method.impl.JobDefinitionMethodImpl.prepareInt(JobDefinitionMethodImpl.java:871)
  at com.redwood.scheduler.model.JobDefinitionImpl.prepareInt(JobDefinitionImpl.java:3008)
  at com.redwood.scheduler.model.method.impl.JobGroupMethodImpl.createJobInt(JobGroupMethodImpl.java:345)
  at com.redwood.scheduler.model.JobGroupImpl.createJobInt(JobGroupImpl.java:1296)
  at com.redwood.scheduler.core.JobGroupUpdater$PresubmitJobsIterator.getNext(JobGroupUpdater.java:638)
  at com.redwood.scheduler.core.JobGroupUpdater$PresubmitJobsIterator.<init>(JobGroupUpdater.java:355)
  at com.redwood.scheduler.core.JobGroupUpdater.rescheduleAll(JobGroupUpdater.java:1117)
  at com.redwood.scheduler.core.JobGroupUpdater.rescheduleJobGroup(JobGroupUpdater.java:856)
at com.redwood.scheduler.action.impl.RescheduleJobGroupActionProcessor.rescheduleJobGroup(RescheduleJobGroupActionProcessor.java:658)
  at com.redwood.scheduler.action.impl.RescheduleJobGroupActionProcessor.access$3(RescheduleJobGroupActionProcessor.java:648)
at com.redwood.scheduler.action.impl.RescheduleJobGroupActionProcessor$3.performWork(RescheduleJobGroupActionProcessor.java:460)
  at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWorkManager.java:14)
  at com.redwood.scheduler.apiint.model.UnitOfWorkManager.perform(UnitOfWorkManager.java:30)
at com.redwood.scheduler.action.impl.RescheduleJobGroupActionProcessor.rescheduleJobGroup(RescheduleJobGroupActionProcessor.java:448)
  at com.redwood.scheduler.action.impl.RescheduleJobGroupActionProcessor.rescheduleJobGroupRetry(RescheduleJobGroupActionProcessor.java:325)
  at com.redwood.scheduler.action.impl.RescheduleJobGroupActionProcessor.execute(RescheduleJobGroupActionProcessor.java:172)
  at com.redwood.scheduler.action.ActionWorker.doWork(ActionWorker.java:87)
  at com.redwood.scheduler.action.ActionWorker.doWork(ActionWorker.java:54)
  at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:81)
  at java.lang.Thread.run(Thread.java:763)


The following Processes are affected:

  • System_UpdateJobStatistics
  • System_DeleteJobFiles
  • System_Ignored_Alert_Reporter
  • System_ProcessKeepClauses

The processes in the Monitor have an old ProcessDefinition, they all seem to have been updated by the "System_Upgrade" Process, after updating the Scheduler.

Since these are System-Processes, we cannot reschedule them, neither can we select the fitting SubmitFrame when trying to schedule them anew.

We tried rebooting the System several times, always with new OP-Messages, reading the Error above.

How can we solve this ASAP, we plan on updating our production system this Sunday, unless we can't fix this.

Thank you!

Jonas

Edit:

Our BPA-Version is 9.0.14.2

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Oct 24, 2015 at 05:01 PM

    I recommend creating a high priority incident with SAP.

    Alternate workaround, since these jobs are not getting scheduled by the system itself, you can manually schedule them to the same submit frame as a temporary fix.

    thanks

    Nanda

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 06, 2015 at 11:22 AM

    Hi,

    We also faced similar issue post upgrade to BPA; Please check the default queue hard coded in the given processes, and check the process servers associated with these queue is up and running fine.

    there might be possibilities that the queue might got changed to different queue during upgrade , once the resources are corrected (queue and process server..) right click on operator message and reply with ""Y"" the jobs will get rescheduled automatically.

    KR

    Muhammad Asif.

    Add comment
    10|10000 characters needed characters exceeded