> No idea yet, except that the transaction state is conflicting with the
> resource manager state. If multiple threads are accessing the token, it
> could be a race, although each thread should have its own transaction.
> 
> I'll file a bug to keep track of the issue (#3935).
> 
> Remy


Thanks Remy. I'll try adding some synchronisation in the short term to
ensure that this sort of thread problem isn't the cause - however,
looking at my code, it definately can't be sharing a token across
different threads (though different threads can and probably do have
seperate tokens in use at the same time).

I don't know how any of the resource manager/transaction stuff works (at
all), so I may be way off, but my impression is that this sort of thing
is _meant_ to be completely safe.

Michael

Reply via email to