Chathura
I had checked in a fix for this already that prevented multiple threads
from actually even getting queued to process timeouts, if one instance
is already running.. So this should be fine now anyway.. Paul.. can you
confirm this from your tests?
asankha
Chathura Ekanayake wrote:
Hi Paul,
The exception you have pointed out is caused by a concurrent issue in
the TimeoutHandler.
It accesses an iterator of the callbackStore, which can also be
modified concurrently by the SynaspeCallbackReceiver.
I made it synchronized, so that it should not occur now.
Chathura
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
