This content has been marked as final. Show 1 reply
I solved it by creating a new command instance in my JMS command executor. But it is not safe because the token might be in another node,
You mean when the async method returns, the token can be in another node then what it was when the async action was started? Could be if something els e signalled it. Then you will signal it again this way and not get the result you wanted. Reloading it with the context it was created in is imo not right (but I might overlook something. The internals of jBPM are not 100% known to me) Why not
1: prevent other code from signalling the token or
2: use additional info (node id or whatever) and check if this is also the same. If not, throw an 'token already signalled' exception or something like that.