java.net.SocketException: Socket closed


Samebug tips2

It's possible you're trying to write to a connection that's already closed. Another cause for this is that you closed the socket with unread data in the socket receive buffer.


7 months ago
Expert tip

This might be caused by unmatching versions of SSL. Java starts normally with SSLv2 and your server might not be able to negotiate. You have to force Java to use SSLv3. See this comment: https://goo.gl/hx0YB3


7 months ago
Expert tip

Solutions on the web1

Solution icon of sourceforge
Socket closed

Stack trace

java.net.SocketException: Socket closed
	at org.sblim.wbem.client.CIMClientXML.transmitRequest(CIMClientXML.java:1750)
	at org.sblim.wbem.client.CIMClientXML.associators(CIMClientXML.java:437)
	at org.sblim.wbem.client.CIMClient.associators(CIMClient.java:558)
	at com.ibm.csm.hchmc.CIMClientEnumeration.enumPowerManagementAlarmDevices(CIMClientEnumeration.java:428)
	at com.ibm.csm.hchmc.CIMClientEnumeration.run(CIMClientEnumeration.java:208)
Caused by: java.net.SocketException: Socket closed
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:155)
	at com.ibm.jsse2.a.a(a.java:188)
	at com.ibm.jsse2.a.a(a.java:232)
	at com.ibm.jsse2.pc.a(pc.java:211)
	at com.ibm.jsse2.pc.g(pc.java:376)
	at com.ibm.jsse2.pc.a(pc.java:573)
	at com.ibm.jsse2.pc.startHandshake(pc.java:37)
	at org.sblim.wbem.http.HttpClient.resetSocket(HttpClient.java:884)
	at org.sblim.wbem.http.HttpClient.connect(HttpClient.java:324)
	at org.sblim.wbem.http.HttpUrlConnection.connect(HttpUrlConnection.java:89)
	at org.sblim.wbem.client.CIMClientXML.transmitRequest(CIMClientXML.java:1745)
	... 4 more

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Once, 3 weeks ago
Samebug visitor profile picture
Unknown user
Once, 3 weeks ago
Once, 1 month ago
Once, 2 months ago
2129 times, 3 months ago
435 more bugmates