Usually, the jobs gets executed pretty much quickly. Factors that might be delaying the execution of jobs is a slow database.
How many concurrent messages is the process expecting? On Jul 12, 2017 13:38, "Gangadhar ireddy" <[email protected]> wrote: We are waiting for the jobs and it releases many times, but few times it doesn't release, Is there any limit on the rescheduling? Regards, Gangadhar. On Wed, Jul 12, 2017 at 1:14 PM, Sathwik B P <[email protected]> wrote: > This is normal. Concurrent messages are competing for the instance lock. > Job that doesn't get the lock on the instance has to wait and will be > rescheduled. > You should never clear the job table. > > On Jul 12, 2017 12:08, "Gangadhar ireddy" <[email protected]> > wrote: > > Sathwik, > > Please find the below log, > > <message><SubProcess24Task137Output><SubProcess24Task137Output > xmlns="http://www.altair.com/EPM/Schema/SubProcess24Task137"; > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:tns="http://www.altair.com/EPM/Schema/SubProcess24Task137";>< > humanTaskInvokeResponse > xmlns="http://www.altair.com/WF/Framework/HumanTaskDataSchema"; > xmlns:htds="http://www.altair.com/WF/Framework/HumanTaskDataSchema";>true</ > humanTaskInvokeResponse></SubProcess24Task137Output></ > SubProcess24Task137Output></message> > 424519845 [ODEServer-513] ERROR > org.apache.ode.scheduler.simple.SimpleScheduler - Error while > processing a persisted job: Job hqejbhcnphrcfcpvi9xhf3 time: > 2017-07-11 14:01:07 EDT transacted: true persisted: true details: > JobDetails( instanceId: 48210 mexId: 50968 processId: null type: > INVOKE_RESPONSE channel: 423 correlatorId: null correlationKeySet: > null retryCount: 1 inMem: false detailsExt: {}) > org.apache.ode.bpel.iapi.Scheduler$JobProcessorException > at org.apache.ode.bpel.engine.BpelEngineImpl.acquireInstanceLock( > BpelEngineImpl.java:394) > at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob( > BpelEngineImpl.java:403) > at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob( > BpelServerImpl.java:450) > at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$ > 1.call(SimpleScheduler.java:518) > at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$ > 1.call(SimpleScheduler.java:512) > at org.apache.ode.scheduler.simple.SimpleScheduler. > execTransaction( > SimpleScheduler.java:284) > at org.apache.ode.scheduler.simple.SimpleScheduler. > execTransaction( > SimpleScheduler.java:239) > at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob. > call(SimpleScheduler.java:512) > at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob. > call(SimpleScheduler.java:496) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > 424519851 [ODEServer-518] ERROR > org.apache.ode.scheduler.simple.SimpleScheduler - Error while > processing a persisted job: Job hqejbhcnphrcfcpvi9xhem time: > 2017-07-11 14:01:05 EDT transacted: true persisted: true details: > JobDetails( instanceId: 48210 mexId: 50955 processId: null type: > INVOKE_RESPONSE channel: 269 correlatorId: null correlationKeySet: > null retryCount: 1 inMem: false detailsExt: {}) > > > Regards, > > Gangadhar. > > > On Tue, Jul 11, 2017 at 12:08 PM, Sathwik B P <[email protected]> > wrote: > > > There are multiple factors for intermittent issues. I can only speculate > > here with limited information. > > > > Check your logs for failures when it happens and share it here, so that > we > > can help you better. If possible put in a sample process to reproduce > your > > scenario and share here. > > > > > > > > > > > > On Tue, Jul 11, 2017 at 9:55 AM, Gangadhar ireddy < > > [email protected]> wrote: > > > > > Sometimes the activity gets released, if it is due to failures in the > > > process, it should fail every time right? > > > > > > Regards, > > > Gangadhar. > > > > > > On Mon, Jul 10, 2017 at 7:06 PM, Sathwik B P <[email protected]> > > wrote: > > > > > > > Jobs might be getting rescheduled due to failures in the process. > > > > Check the logs for errors. > > > > > > > > On Mon, Jul 10, 2017 at 10:12 AM, Gangadhar ireddy < > > > > [email protected]> wrote: > > > > > > > > > Hi Sathwik, > > > > > > > > > > I can see INVOKE_RESPONSE type in ode_jobs table,for some tasks it > > will > > > > be > > > > > updated with INVOKE_CHECK from INVOKE_RESPONSE. Sometimes it takes > > more > > > > > time to release the tasks, sometimes it will not release. > > > > > > > > > > Regards, > > > > > Ganga. > > > > > > > > > > On Fri, Jul 7, 2017 at 5:04 PM, Sathwik B P <[email protected]> > > > > wrote: > > > > > > > > > > > What kind of jobs are pending? > > > > > > What activities do you have within your <flow>? > > > > > > > > > > > > regards, > > > > > > sathwik > > > > > > > > > > > > On Fri, Jul 7, 2017 at 2:13 PM, Gangadhar ireddy < > > > > > > [email protected] > > > > > > > wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > This is Gangadhar working for Altair, currently we are using > > > > Apache-ode > > > > > > and > > > > > > > facing few issues on flow activity. > > > > > > > > > > > > > > 1. Sometimes all the activities will not be released and when i > > > check > > > > > the > > > > > > > ode_job table there are some records not getting updated. But > > when > > > i > > > > > > clean > > > > > > > ode_job table and create a new instance it works fine. > > > > > > > > > > > > > > 2. If i have more than 9 activities in flow , it takes large > > amount > > > > of > > > > > > time > > > > > > > to release all the tasks. > > > > > > > > > > > > > > > > > > > > > Can you help me to fix these issues. > > > > > > > > > > > > > > Thanks, > > > > > > > Gangadhar. > > > > > > > > > > > > > > > > > > > > > > > > > > > >
