Hi Asankha,
> If you suspect this has something to do with SSL/JDK, then the debug
> options at
> http://java.sun.com/j2se/1.5.0/docs/guide/security/jsse/JSSERefGuide.html#Debug
> might be of interest. The -Djavax.net/debug=all would dump a lot of
> handshake information, which may help you figure out the problem.
Thanks for the tip. It worked better than expected: when I switch
on debug output, the test runs through. When I switch it off, it
hangs again. I get the feeling that this is a threading issue in
the test. There's a very suspicious "Thread.yield()" in there.
The test also makes permanent modifications by setting system
properties, which could affect all subsequent tests running in
the JVM. I have a bad feeling about this.
For now, I'll take the easy way out and switch to the text-based
test runner. <junit> is really only of advantage for tests that
write to System.{out|err}, or if several test cases fail. Neither
is or should be the case for ours.
thanks,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
