Details
-
Bug
-
Resolution: Done
-
Major
-
2.3.1.Final
-
None
Description
Lot's of these can be observed when the engine is under the load 60-75 messages per second.
2011-10-14 10:59:00,766 ERROR [org.apache.ode.scheduler.simple.SimpleScheduler] (ODEServer-183) Error loading immediate jobs from database. java.lang.NullPointerException at org.apache.ode.scheduler.simple.SimpleScheduler.doLoadImmediate(SimpleScheduler.java:765) at org.apache.ode.scheduler.simple.SimpleScheduler$LoadImmediateTask.run(SimpleScheduler.java:864) at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:721) at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:718) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)
A simple BPEL process with start-invokeWS-end can be used to reproduce this exception.
