United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 6984182 Setting SO_RCVBUF/SO_SNDBUF to larger than tcp_max_buf fails on Solaris 11 if kernel params changed
6984182 : Setting SO_RCVBUF/SO_SNDBUF to larger than tcp_max_buf fails on Solaris 11 if kernel params changed

Details
Type:
Bug
Submit Date:
2010-09-13
Status:
Closed
Updated Date:
2012-03-22
Project Name:
JDK
Resolved Date:
2011-03-08
Component:
core-libs
OS:
solaris
Sub-Component:
java.net
CPU:
x86
Priority:
P2
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:
7

Related Reports
Backport:
JDK-2205485 - Setting SO_RCVBUF/SO_SNDBUF to larger than tcp_max_buf fails on Solaris 11 if kernel params changed
Backport:
JDK-2206133 - Setting SO_RCVBUF/SO_SNDBUF to larger than tcp_max_buf fails on Solaris 11 if kernel params changed
Backport:
JDK-2205353 - Setting SO_RCVBUF/SO_SNDBUF to larger than tcp_max_buf fails on Solaris 11 if kernel params changed
Relates:
JDK-6989190 - SO_SNDBUF/SO_RCVBUF limits should only be checked when setsockopt fails (sol)
Relates:
JDK-6984545 - (fc) transferFrom does not throw NonReadableChannelException when target is size 0 and non-readable
Relates:
JDK-6431344 - (fc) FileChannel.transferTo() doesn't work if address space runs out

Sub Tasks

Description
tests

api/java_nio/channels/AsynchronousServerSocketChannel/AsynchronousServerSocketChannel.html#NetworkChannel[getSet_SO_RCVBUF_test]
api/java_nio/channels/AsynchronousSocketChannel/AsynchronousSocketChannel.html#NetworkChannel[getSet_SO_RCVBUF_test]
api/java_nio/channels/FileChannel/index.html#Methods[FileChannel0024]
api/java_nio/channels/ServerSocketChannel/ServerSocketChannel.html#NetworkChannel[getSet_SO_RCVBUF_test]
api/java_nio/channels/SocketChannel/SocketChannel.html#NetworkChannel[getSet_SO_RCVBUF_test]

fail starting jdk 7 b109. Pass b108.
seems to be solaris11-specific

Comments
EVALUATION

6989190 is tracking the first step to resolving this one. Once 6989190 is in a promoted build (probably b114) then the fallback values will correspond to the default limits (1MB for tcp, 2MB for udp) and and so the JCK failures reported should disappear. We are still left with the scenario where these parameters have been changed from their default value so I will keep this bug open to track that.
2010-10-04 
EVALUATION

api/java_nio/channels/FileChannel/index.html#Methods[FileChannel0024] is a genuine failure and arises when FileChannel.transferFrom(ReadableByteChannel,long,long) is called with a FileChannel that is not readable and the file size is 0. I've separated this one out into its own bug: 6984545.

The other failures are Solaris 11 specific. When setting SO_RCVBUF or SO_SNDBUF then we query the /dev/tcp driver's tcp_max_buf property to limit the size. This is done with the ND_GET command and the I_STR ioctl. This is failing on snv146 (okay in snv122, which some of our test machines have). It turns out that this interface has been removed in Solaris 11 and so we need to find another way to get the value of tcp_max_buf.
2010-09-14


Hardware and Software, Engineered to Work Together