AsynchronousSocketChannel still throws unspecified exception

[Alan Bateman]

cowwoc wrote:
> :
> Now I'm getting really worried... I just noticed that socket timeouts are
> wrong as well!
>
> If you recall, we had agreed that a timeout value of 0 or less should mean
> "no timeout" and Long.MAX_VALUE should mean "wait forever":
> http://web.archiveorange.com/archive/v/gpYtBv5dfSke8QjCflUY
>   
Yes, I remember that discussion and we changed it, via 6878369, so that 
<= 0 means that the I/O operation doesn't have a timeout (previously it 
was specified to throw IllegalArgumentException if a negative timeout 
was specified).

-Alan.