ok, I partly mixed 2 things up.... but... nevertheless, the one/multiple threads thing of the jobexecutor was never explicitly meant to work (nor was it not meant to work) and no, I was not saying there should be one mdb but maybe the behaviour when jms is involved is different.... and why is it not enough to have multiple timers on one processinstance but have them processed one after the other... prevents locking to. Multiple threads could probably work then.
Still....I think that concurrent access to tokens is another issue... what should the behaviour be in those cases.... rather hard to decide....So is it a theoretical(?) case for workflow? I agree that the second timer should not fail, but rather report something like 'nothing to process anymore' correct?... Someone should try to describe some real scenario's so we can decide what the behaviour should be. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056218#4056218 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056218 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
