Sockets are built on top of the public class SocketImpl which extends SocketOptions.
SocketOptions.getOption and SocketOptions.setOption both specifically
define in their spec that
* @throws SocketException if the socket is closed
In practice, on Solaris this does not happen. The socket can be closed
and the Socket.getXXX methods do NOT get an exception.
Attached is a simple test program that demonstrates that getSoTimeout continues
to work after the socket is closed.
I have set the severity high because JavaTest (used in JCK) requires some
way of testing whether a socket has been closed or not. Given a suitable
workaround, I will lower the severity.
SocketOptions.getOption and SocketOptions.setOption both specifically
define in their spec that
* @throws SocketException if the socket is closed
In practice, on Solaris this does not happen. The socket can be closed
and the Socket.getXXX methods do NOT get an exception.
Attached is a simple test program that demonstrates that getSoTimeout continues
to work after the socket is closed.
I have set the severity high because JavaTest (used in JCK) requires some
way of testing whether a socket has been closed or not. Given a suitable
workaround, I will lower the severity.
- duplicates
-
JDK-4283912 setSoTimeout()/getSoTimeout() don't throw exceptions when the socket is closed
-
- Closed
-