>> 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.
But threadB could call the finishConnect method only after we set the
OP_CONNECT interest in threadA. And we set that interest after
CountDownLatch initialization.
Thanks.
WBR,
Alexey.
>
>
>
> Thanks
> Sebastian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>