FULL PRODUCT VERSION :
1.7.0_09 (32bit)
ADDITIONAL OS VERSION INFORMATION :
OS : RedHat Enterprise Linux 6.2 (64bit)
Kernel ?2.6.32-220.23.1.el6.x86_64
A DESCRIPTION OF THE PROBLEM :
We've built an environment with 1.7.0_09 (32bit) JVM on RHEL6.2 (64bit) and ran a test program that execute's java.net.ServerSocket.accept() method with infinite timeout.
At the same time, we've accelerated the cpu's uptime.
As a result, we always get java.net.SocketTimeoutException in 49.7 days
(2^32 milli-seconds) as we expected. Any idea on what the cause is ?
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
No SocketTimeoutException occurs and keeps on waiting for connection.
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
ServerSocket serverSocket = new ServerSocket(5555);
serverSocket.accept();
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
Not found. Need to restart the program to avoid SocketTimeoutException.
1.7.0_09 (32bit)
ADDITIONAL OS VERSION INFORMATION :
OS : RedHat Enterprise Linux 6.2 (64bit)
Kernel ?2.6.32-220.23.1.el6.x86_64
A DESCRIPTION OF THE PROBLEM :
We've built an environment with 1.7.0_09 (32bit) JVM on RHEL6.2 (64bit) and ran a test program that execute's java.net.ServerSocket.accept() method with infinite timeout.
At the same time, we've accelerated the cpu's uptime.
As a result, we always get java.net.SocketTimeoutException in 49.7 days
(2^32 milli-seconds) as we expected. Any idea on what the cause is ?
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
No SocketTimeoutException occurs and keeps on waiting for connection.
REPRODUCIBILITY :
This bug can be reproduced always.
---------- BEGIN SOURCE ----------
ServerSocket serverSocket = new ServerSocket(5555);
serverSocket.accept();
---------- END SOURCE ----------
CUSTOMER SUBMITTED WORKAROUND :
Not found. Need to restart the program to avoid SocketTimeoutException.