[
https://jira.jboss.org/jira/browse/JBPM-1798?page=com.atlassian.jira.plug...
]
Alejandro Guizar reassigned JBPM-1798:
--------------------------------------
Assignee: Tom Baeyens (was: Alejandro Guizar)
JBPM1798Test used to affect other tests because the job executor was started but never
stopped. After replacing the startJobExecutor() call with processJobs(), the test no
longer affects other tests. However, I still cannot reproduce the NPE. Any stack trace or
other information?
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: Tom Baeyens
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira