java.net.SocketException

If you like a tip written by other Samebug users, mark is as helpful! Marks help our algorithm provide you better solutions and also help other users.
tip

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.


rafael
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


rafael

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

  • Java.net Connection Reset using Rserve
    via Stack Overflow by Vini
    ,
  • Interacting with R via Java Programs
    via Stack Overflow by nynoles
    ,
  • How to import R script in java
    via Stack Overflow by peter
    ,
  • GitHub comment 364#274155958
    via GitHub by dpwspoon
    ,
  • Connect 2 simulators on host on same machine
    via by Gareth Murfin,
  • pgpool Bug Tracker
    via by Unknown author,
    • java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:209) at java.net.SocketInputStream.read(SocketInputStream.java:141) at java.net.SocketInputStream.read(SocketInputStream.java:127) at org.rosuda.REngine.Rserve.protocol.RTalk.request(RTalk.java:213) at org.rosuda.REngine.Rserve.protocol.RTalk.request(RTalk.java:180) at org.rosuda.REngine.Rserve.protocol.RTalk.request(RTalk.java:250) at org.rosuda.REngine.Rserve.RConnection.eval(RConnection.java:231) at integration.Integration.main(Integration.java:36)

    Users with the same issue

    ivanszkypeter
    40 times, last one,
    linxiaolong
    2 times, last one,
    Unknown visitor1 times, last one,
    tvrmsmith
    1 times, last one,
    Unknown visitor1 times, last one,
    263 more bugmates