[CXF-4857] Workaround for Socket Closed exception with some JDK 1.6.0_nn (>= 38)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.5, 2.7.3
• Fix Version/s: 2.7.4, 2.6.7, 3.0.0-milestone1
• Component/s: Transports
• Estimated Complexity: Unknown
• Assignee: Akitoshi Yoshida
• Reporter: Akitoshi Yoshida
• Created: 26/Feb/13 15:42
• Updated: 09/Apr/13 15:15
• Resolved: 04/Apr/13 10:00

Description

With recent Oracle jdk1.6.0_38 (including the latest jdk1.6.0_41) on Windows and Linux, we are observing the Socket Closed exception.

The exception is shown as
Caused by: java.net.SocketException: Socket Closed
at java.net.PlainSocketImpl.getOption(PlainSocketImpl.java:286)
at java.net.Socket.getSoTimeout(Socket.java:1032)
at sun.net.www.http.HttpClient.available(HttpClient.java:356)
at sun.net.www.http.HttpClient.New(HttpClient.java:273)
at sun.net.www.http.HttpClient.New(HttpClient.java:310)
at
sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLCon
nection.java:987)
at
sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnect
ion.java:923)
at
sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.j
ava:841)
at
sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConn
ection.java:1031)
at
org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWra
ppedOutputStream.setupWrappedStream(URLConnectionHTTPConduit.java:170)
at

So far the issue is only observed with some JDK versions and not with others (e.g. OSX or Win/Linux 1.7.0_nn versions).

Until this issue is clarified, I am proposing to add a small workaround in CXF to avoid this issue.

Issue Links

• is related to: CXF-4846 A confusing exception may be thrown from HTTPConduit when oneway call results in HTTP 500 response