I found the origin of the problem in my case. The problem was neither the
synchronization nor the connection gone. It was that the asynchronous
writing started too early, before the connection was completely established,
speaking losely...
When I made sure that the writing starts *after* all t
xception
(InvalidCxnException or so) would be better, since it can be caught
intentionally. Or return silently, if there is no other chance.
Cheers
FFD
1000MIKES.COM
Filip Hanik - Dev Lists wrote:
>
> a NPE probably has nothing to do with synchronization, more like you are
> trying to