On Tue, Oct 21, 2008 at 3:36 PM, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote:
>> Ok, I did it, but it didn't help :-(
> At least, this is not the same NPE :)
:-)
> Without the check, as the getConnectionRequest() method can return null for
> the very same reason than the previously fixed accept() method, you will
> have a NPE.
Right.
> I have committed a patch for this case. Can you run another test ?
Yepp, I did.
However it yielded the following log messages only:
16:44:01.530 [pool-1-thread-1] DEBUG test - Before connect...
16:44:01.546 [pool-1-thread-1] DEBUG test - After connect...
16:44:01.546 [pool-1-thread-1] DEBUG test - Before await...
And nothing else.
The same code from a standalone application produces the following log
messages (I added an additional logging line here:
logger.debug("Before await...");
cf.awaitUninterruptibly();
logger.debug(cf.getException().getMessage());
logger.debug("After await...");
)
16:50:48.796 [main] DEBUG test - Before connect...
16:50:48.812 [main] DEBUG test - After connect...
16:50:48.812 [main] DEBUG test - Before await...
16:50:49.718 [main] DEBUG test - Connection refused: no further information
16:50:49.718 [main] DEBUG test - After await...
It's OK if I get the connection refused message as there are nothing
listening on the address I use, but then why don't I get the same
error from the web application? It seems that the
waitUninterruptably() call just waits, but it doesn't terminate when
the connection attempt is unsuccessful. Somehow it makes sense, as the
ConnectionRequest is null, so I wouldn't wait for it to somehow
provide a proper, terminating ConnectFuture.
I hope it makes sense for you.
> (I'm currently installing glassfish, but it will take a bit to have it up
> and running)
Well, good luck with that :-)
--
Zizi
"Oh, by the way... Anyone still experiencing stress by the end of the
day... WILL BE FIRED!!!"
