Now I'm having trouble under 1.5 too, on my laptop.
Looking at a thread dump, it seems like the SO_TIMEOUT is ignored,
and also interrupting a thread in a ServerSocketChannel blocking accept
doesn't have any effect at all.
Aaron
-- This class hangs when run:
public class Temp {
public static void main(String[] args) {
try {
ServerSocketChannel ssc = ServerSocketChannel.open();
ssc.socket().bind(new InetSocketAddress(InetAddress.getLocalHost(),
2010),50);
ssc.socket().setSoTimeout(5000);
System.out.println("accepting...");
ssc.accept();
} catch (IOException e) {
e.printStackTrace();
}
System.out.println("Finished");
}
}
-- A similar test with only a ServerSocket runs fine.
On Sun, 31 Oct 2004, Jeremy Boynes wrote:
> Can you add these configs to the Known(not)Working page on the wiki.
>
> Aaron Mulder wrote:
> > FYI, I have upgraded my Linux machines to SuSE 9.2 (SuSE kernel
> > 2.6.8-24.3). On one of them, with JDK 1.4, during an m:rebuild-all, I got
> > a JDK crash in an NIO accept() in the unit tests in our remoting stuff.
> > I got that a few times in a row, then a while later got a test failure
> > instead (with an address in use during bind) also in the remoting tests.
> > I tried JDK 1.4.2_05 and _06 and both had the problem. On another machine
> > with the same distro/kernel, JMXRemotingTest hangs (both sides of the asyc
> > conversation seem to be blocked on read).
> >
> > In any of these cases JDK 1.5 seems fine, so I'm guess there is
> > some sort of kernel compatibility problem with 1.4 NIO networking going
> > on.
> >
> > Aaron
>
>
