potential nullpointer in asynchronous jobs when process ends
------------------------------------------------------------
Key: JBPM-1798
URL:
https://jira.jboss.org/jira/browse/JBPM-1798
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Engine
Reporter: Tom Baeyens
Assignee: Thomas Diesler
Fix For: jBPM 3.2.6 GA
when a process instance ends, a cleaning Job is issued. if that happens when an async
job is outstanding, then it turns out that this may lead to a NPE when the outstanding job
is executed.
use this process to reproduce in an AbstractDbTestCase
ProcessDefinition processDefinition = ProcessDefinition.parseXmlString(
"<process-definition name='customjobexecution'
initial='start'>" +
" <node name='start'>" +
" <transition to='end'>" +
" <action async='true'
class='"+AsyncAction.class.getName()+"' />" +
" </transition>" +
" </node>" +
" <end-state name='end' />" +
"</process-definition>"
deploy and start it
new Transaction()
then start the job executor with startJobExecutor()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: