Hi kasabov, I had the same problem. Configure in the web.xml the following listener
| <listener> | <description> | Starts the job executor on servlet context initialization and stops it on | servlet context destruction. | </description> | <listener-class>org.jbpm.web.JobExecutorLauncher</listener-class> | </listener> | This will start the jobscheduler You can also configure the following servlet, that's optional, only for information on jobScheduler health | <servlet> | <description> | This servlet has the purpose of executing pending jobs. Deprecated, | replaced by JobExecutorLauncher. | </description> | <servlet-name>JobExecutorServlet</servlet-name> | <servlet-class>org.jbpm.job.executor.JobExecutorServlet</servlet-class> | <load-on-startup>1</load-on-startup> | </servlet> | <servlet-mapping> | <servlet-name>JobExecutorServlet</servlet-name> | <url-pattern>/jobs</url-pattern> | </servlet-mapping> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205200#4205200 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205200 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
