> TCPConnectorHandler.setConnectionTimeout(0);
Thanks a lot for this hint! I'll give this a try right now.
> Hmm... Not sure I understand where the problem could occur :)
> at line 280 threadA creates CountDownLatch(1), and never changes it again,
> right?
> ThreadB could call finishConnect either at time threadA will execute line
> 282 or later. ThreadB can modify CountDownLatch, its internal state, not a
> reference.
No, the issue which I'm wondering about is that threadB might not see
the new instance of CountDownLatch and get null when it tries to read
the isConnectedLatch field at line 597, since lack of synchronization.
Thanks
Sebastian