JDK-5103050 : NNTPClient client.connect break at jdk 1.4.2
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.net
  • Affected Version: 1.4.2_06
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_8
  • CPU: sparc
  • Submitted: 2004-09-16
  • Updated: 2004-09-27
  • Resolved: 2004-09-27
Related Reports
Duplicate :  
JDK-5019401 - ServerSocket(Proxy) and Socket(Proxy) do not work with sun one proxy server
Duplicate :  
JDK-5103052 - NNTPClient client.connect break at jdk 1.4
Description
The behaviour is different for 1.4.2
###@###.### 2004-09-16
Comments
EVALUATION This does not happen in 1.4.2 without -DsocksProxyHost=<host> property. This is applicable to Win2K also. When used, a new SocksSocketImpl is created by the Factory to handle the SOCKS V4/V5 support. To transmit SOCKS commands, 1.3.1 uses ByteArrayOutputStream 1.4.2 uses DataOutputStream 1.5.0 uses BufferedOutputStream With DataOutputStream, the bytes are sent for each .write() call. The problem is with the time spent in data transmission. In 1.4.2, with DataOutputStream there are some time being spend in sending the full 'CONNECT' command which is of 10 byte length. Using the same Stream, if all the 10 bytes are written at one shot, it works fine. So, changing DataOutputStream to BufferedOutputStream is a nice way to go. ###@###.### 2004-09-21 The fix for this bug has been done already as part of bug 5019401 fix. I'm closing this bug as duplicate of 5019401. ###@###.### 2004-09-27
21-09-2004