This content has been marked as final.
Show 6 replies
-
1. Re: Allow unlocking Token without knowing the lock owner
camunda Nov 25, 2008 10:57 AM (in response to camunda) -
2. Re: Allow unlocking Token without knowing the lock owner
camunda Nov 26, 2008 3:28 AM (in response to camunda)If nobody is against that I will just go ahead on Friday (when I am back in office) and fix it...
-
3. Re: Allow unlocking Token without knowing the lock owner
heiko.braun Nov 26, 2008 3:58 AM (in response to camunda)What the purpose of locking a token in the first place?
-
4. Re: Allow unlocking Token without knowing the lock owner
tom.baeyens Nov 26, 2008 4:15 AM (in response to camunda)when an asynchronous continuation happens, the engine knows that the asynchronous message job is supposed to perform the next action.
no external triggers are allowed at that point. -
5. Re: Allow unlocking Token without knowing the lock owner
kukeltje Nov 26, 2008 5:29 AM (in response to camunda)but it is only locked if the job is running right? not when it is still 'sleeping'
-
6. Re: Allow unlocking Token without knowing the lock owner
tom.baeyens Nov 28, 2008 7:56 AM (in response to camunda)the execution is also locked when sleeping.
you are probably mixing with acquisition of jobs before they get executed. that is something else to make sure that a job is only executed once in a clustered env.