Jon,
Threads don't share hibernate caches on the same process instance. If another
thread looks at the token, it's going to have fetched it independently from the
database.
The database is updated when the token reaches a wait state.
I'm still trying to understand what it means that the
anonymous wrote : The database is updated when the token reaches a wait state.
That's what I supposed, but wasn't sure. Thus, that tells me that if a
separate thread gets the node for a token, then that means the token is in a
wait state at that node. I guess it might actually be in the
do you want to manipulate the token from 2 threads, or do you just want to make
sure you know what node it is in? The former is bad practise the second should
be a method on your own first thread and ask there what state the token is in.
View the original post :
Thanks for clarifying. No, I do not want to manipulate the token from the
other thread. I figured that was a no-no. From my other thread I just want to
know what node it is on. We want to provide users with some insight into what
state the workflow is in.
In this case I think it is
