-
1. Re: SchedulerThread.executeTimers() in single tx?
kukeltje Nov 30, 2005 11:31 AM (in response to ralfoeldi)No snow in Switzerland? Lucky me I go to Austria (Flachau) between Xmas and newyear.
Regarding your question. This to me sounds like an ommision in jBPM. Can you file a jira issue for this? -
2. Re: SchedulerThread.executeTimers() in single tx?
ralfoeldi Nov 30, 2005 12:16 PM (in response to ralfoeldi)Hi Ronald,
well there was snow (as in Germany... :-( ) but its all gone and now its just cold and wet (at least in the Zürich / Winterthur area). I wish you luck for Flachau. It isn't all that high is it? 2000m?
I'm not sure if this is a valid Jira issue. I've been nagging about other transaction issues for the past few weeks now and I seem to be the only one who needs (or wants) that kind of detailed demarcation. (Nobody else out there? ... Oh well.)
The solution would be none trivial anyway as I am just noticing.
I just saw that you seem to be fully aware of the issue http://jira.jboss.com/jira/browse/JBPM-46 where Tom states that"we only use one transactional resource (jdbc connection) so ..."
Jira feature request: http://jira.jboss.com/jira/browse/JBPM-452
Rainer -
4. Re: SchedulerThread.executeTimers() in single tx?
ralfoeldi Nov 30, 2005 2:42 PM (in response to ralfoeldi):-) have fun...
-
5. Re: SchedulerThread.executeTimers() in single tx?
koen.aers Nov 30, 2005 4:03 PM (in response to ralfoeldi)Rainer,
It is in any case not difficult to create your own timer execution mechanism if you would like to do that. You can do this with other mechanisms than the servlet spawning a thread, if you would prefer to do so. E.g. using an mbean if you are using JBoss AS.
Regards,
Koen
Btw. We (Tom and I) will be for a day in Wengen in two weeks, so it would better snow! -
6. Re: SchedulerThread.executeTimers() in single tx?
ralfoeldi Nov 30, 2005 4:39 PM (in response to ralfoeldi)Hi Koen,
seems like everybody is going skiing except for me. Looks like I'm doing something wrong and got to get my priorities right. I mean I live in Switzerland now!
It isn't all that complicated but it isn't trivial either. Its just a lot of code loading, detaching, reattaching all effected objects to Hibernate without one transaction getting in the way of the other.
I've already seperated the "normal" execution into some SLSBs and MDBs etc. Thats up and running. Read all about it: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=72642 (don't read it, you already commented.)
What I'm doing now is using Quartz to trigger a SLSB that will retrieve the Timers, call another SLSB to execute the Timer and then delete / save the Timer / ProcessInstance. Its basically the Hibernate plumbing.
I was just hoping... maybe it's already there and I just don't see it.
Have fun in Wengen!
Rainer