[
http://jira.jboss.com/jira/browse/JBPM-1186?page=all ]
Ronald van Kuijk resolved JBPM-1186.
------------------------------------
Resolution: Done
Implemented:
public void destroy() {
super.destroy();
jbpmConfiguration.close();
}
jobexecutor (threads) not stopped when JobExecutorServlet is
destroyed
----------------------------------------------------------------------
Key: JBPM-1186
URL:
http://jira.jboss.com/jira/browse/JBPM-1186
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.2
Reporter: Ronald van Kuijk
Assigned To: Ronald van Kuijk
Fix For: jBPM jPDL 3.2.3
Original Estimate: 20 minutes
Remaining Estimate: 20 minutes
According to the javadoc of the jobexecutor servlet:
/**
* starts the job executor on init and closes the
* jbpm configuration upon destroy. The closing of the
* jbpm configuration will also shut down the job executor
* thread pool.
There is no destroy method, so nothing wil happen. Threads keep running. Secondly,
I'm not sure closing the jBPM context is what we want there. Can't we just call
jobExecutor.stop()? In case we just want to stop it?
A stop/start method on the servlet with a param is also handy.... e.g. from the
webconsole????
--
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