This content has been marked as final.
Show 2 replies
-
1. Re: CommandExecutorThread not started in Jbpm3.1, Jboss4.0.3
jits_1998 Sep 15, 2006 2:45 AM (in response to doromoji)The command executor thread is expected to be running for any signal processing to happen in async environment.
There is no configuration required to run it. AFAIK.
Can you specify which version of jbpm are you using?
cheers! -
2. Re: CommandExecutorThread not started in Jbpm3.1, Jboss4.0.3
doromoji Sep 16, 2006 1:01 AM (in response to doromoji)I'm using Jbpm3.1.
I found that log4j.xml in Jboss need to change to TRACE level, so that the CommandExecutorThread can print the output in console.
The JbpmThreadsServlet and JbpmContextFilter are also required in the web.xml