[
http://jira.jboss.com/jira/browse/JBPM-1102?page=all ]
Pierre Demeestere updated JBPM-1102:
------------------------------------
Description:
when stopping the application server (tomcat) , a NullPointerException is spotted at line
84 in JobExecutorThread.
That may be because threads are not stopped properly when the JobExecutorServlet is
undeployed.
Indeed, despite source comments in JobExecutorServlet (talking about stopping threads in
destroy method) , nothing is done in this servlet to stop the threads when the servlet is
undeployed.
was:
when stopping application server, a NullPointerException is spotted at line 84 in
JobExecutorThread.
That may be because threads are not stopped properly when the JobExecutorServlet is
undeployed.
Indeed, despite source comments in JobExecutorServlet, nothing is done in this servlet to
stop the threads when the servlet is undeployed.
Despite source comment, JobExecutorServlet does not stop threads on
destroy
---------------------------------------------------------------------------
Key: JBPM-1102
URL:
http://jira.jboss.com/jira/browse/JBPM-1102
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Environment: Windows NT and Linux RH 4
Reporter: Pierre Demeestere
Assigned To: Tom Baeyens
Priority: Minor
when stopping the application server (tomcat) , a NullPointerException is spotted at line
84 in JobExecutorThread.
That may be because threads are not stopped properly when the JobExecutorServlet is
undeployed.
Indeed, despite source comments in JobExecutorServlet (talking about stopping threads in
destroy method) , nothing is done in this servlet to stop the threads when the servlet is
undeployed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira