Hi Dasarath,
We do remove the callback whenever there is a timeout. In fact this happens
even before Callback.timeout() is called:
[..]
Please let me know if I'm missing your point. My thinking is that this problem
is simply the result of Java Timer needing more time to cleanup all the
coordinators under heavy load conditions...
Sorry, I didn't look there for the remove-call. And I overlooked the
fact that not only the transaction ID is registered in the
CallbackRegistry, but also the participant is registered there to handle
the calls.
Upon further investigation I'm now asking myself whether the
participant's callbacks are also removed... ?
Best regards,
-hannes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
