Exception while executing ExecuteJobsCommand on MemoryLockJobExecutor

Hi all BOS Communitty

 

In the JBoss log of the server of my company , it's appearing this error message

Exception while executing ExecuteJobsCommand on MemoryLockJobExecutor

 

I am using JBoss 5 as a Web Server

Database: MS SQL  2008 R2

BOS versión 5.10.1

 

I have configured connection pool for history and journal BOS databases

 

Any suggestions to know what's going on ?

 

Thank you

 

Regards

 

 

Exception while executing ExecuteJobsCommand on MemoryLockJobExecutor
java.lang.NullPointerException
at org.ow2.bonita.runtime.event.ExecuteJobsCommand.executeJob(ExecuteJobsCommand.java:143)
at org.ow2.bonita.runtime.event.ExecuteJobsCommand.execute(ExecuteJobsCommand.java:86)
at org.ow2.bonita.runtime.event.ExecuteJobsCommand.execute(ExecuteJobsCommand.java:47)
at org.ow2.bonita.services.impl.DefaultCommandService.execute(DefaultCommandService.java:44)
at org.ow2.bonita.runtime.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:45)
at org.ow2.bonita.services.impl.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.ow2.bonita.services.impl.RetryInterceptor.execute(RetryInterceptor.java:59)
at org.ow2.bonita.runtime.event.JobExecutorThread.run(JobExecutorThread.java:39)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
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:662)
2014-01-15 11:38:29,949 SEVERE [org.ow2.bonita.services.impl.DefaultCommandService] (pool-22-thread-1) exception while executing command org.ow2.bonita.runtime.event.ExecuteJobsCommand@5bd2a9ba: null
2014-01-15 11:38:29,951 SEVERE [org.ow2.bonita.runtime.event.JobExecutorThread] (pool-22-thread-1) Exception in event block: java.lang.NullPointerException
at org.ow2.bonita.runtime.event.ExecuteJobsCommand.executeJob(ExecuteJobsCommand.java:143)
at org.ow2.bonita.runtime.event.ExecuteJobsCommand.execute(ExecuteJobsCommand.java:86)
at org.ow2.bonita.runtime.event.ExecuteJobsCommand.execute(ExecuteJobsCommand.java:47)
at org.ow2.bonita.services.impl.DefaultCommandService.execute(DefaultCommandService.java:44)
at org.ow2.bonita.runtime.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:45)
at org.ow2.bonita.services.impl.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.ow2.bonita.services.impl.RetryInterceptor.execute(RetryInterceptor.java:59)
at org.ow2.bonita.runtime.event.JobExecutorThread.run(JobExecutorThread.java:39)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
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:662)

You seem to the same issue as Andrés (https://bonita.atlassian.net/browse/BBPMC-110).

Do you have a process containing a boundary timer on multi-instantiated task?

The bug BBPMC-110 was fixed in the version 5.10.2 (already available to download).

Hi all  friends 

 

My fellow "Temple of Steel" has found that  it happens when  there are two versions of a subprocess and one of them is disabled , and several father  cases process of this subprocess are already alive.

 

Then BOS  write this error in log every five seconds 

 

 The solution is to remove all this father cases with the subprocess disabled

 

Hope this help

Regards

Do you have more details about this exception? any stack trace?

Its seems that the Bonita Engine is trying to execute a job for a execution that doesn't exist anymore. Do you reproduce this systematically? wich are the steps to reproduce this issue?

 

How do I identify the father cases with sub-processes disabled to remove them?