[JBoss jBPM] - Re: Dying processes problem
by kukeltje
"Turanyi" wrote :
| Imagine: I deploy process. Everything is ok. Process works.
|
It can't just work... process INSTANCES have to be started or signalled
"Turanyi" wrote :
| Now I stop JBoss server by ctrl+c. Server shutdown.
| Ok, this should not be a problem"Turanyi" wrote :
| After some time I start JBoss server and I see problems with deploy process from tmp...
What deploy processes from tmp? What problems?
"Turanyi" wrote :
| I look to jbossws console and I see prosess is not started. Process not respond, process is dead.
| jbossws console? Never heard of that... process not responding?if it is persistant in the database you have to signal PROCESS INSTANCES again to continue to the next state... does not happen automagically
"Turanyi" wrote :
| I have to deploy it again to use it.
| never heard of that...did you build custom code?"Turanyi" wrote :
| WTF. Is it normal?
Please no swearing... even I have never done that
You have to be way more specific for us to be able to help you
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179823#4179823
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179823
15 years, 9 months
[JBoss jBPM] - Re: Timers in jBPL
by juergen_lampe
I think so. It should be started via the web.xml entry:
<!-- Job executor launcher (begin) -->
| <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>
| <!-- Job executor launcher (end) -->
|
Meanwhile I played around a bit:
1) changed the timer to
<timer name='reminder'
| duedate='2 minutes'
| transition='ex1' >
| <script>
| System.out.println("Timer fired "+node);
| Token.signal();
| </script>
| </timer>
|
got the output "Timer fired State(warte 1)" but nothing else.
2) changed the script to
<script>
| System.out.println("Timer fired "+node);
| executionContext.getProcessInstance().signal();
| </script>
|
found the server locked in endless printing "Timer fired State(warte 1)"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179782#4179782
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179782
15 years, 9 months