java.net.SocketException

Software caused connection abort: recv failed

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.

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

Don't give up yet. Our experts can help. Paste your full stack trace to get a solution.

Solutions on the web7075

  • via GitHub by RiPex-Rain
    , 1 year ago
    Software caused connection abort: recv failed
  • Software caused connection abort: recv failed
  • via Google Groups by edh, 1 year ago
    Software caused connection abort: recv failed
  • Stack trace

    • java.net.SocketException: Software caused connection abort: recv failed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at jcifs.util.transport.Transport.readn(Transport.java:29) at jcifs.smb.SmbTransport.peekKey(SmbTransport.java:388) at jcifs.smb.SmbTransport.negotiate(SmbTransport.java:288) at jcifs.smb.SmbTransport.doConnect(SmbTransport.java:319) at jcifs.util.transport.Transport.run(Transport.java:241) at java.lang.Thread.run(Unknown Source) at jcifs.util.transport.Transport.run(Transport.java:258) at java.lang.Thread.run(Unknown Source) at jcifs.smb.SmbTransport.connect(SmbTransport.java:309) at jcifs.smb.SmbTree.treeConnect(SmbTree.java:156) at jcifs.smb.SmbFile.doConnect(SmbFile.java:911) at jcifs.smb.SmbFile.connect(SmbFile.java:954) at jcifs.smb.SmbFile.connect0(SmbFile.java:880) at jcifs.smb.SmbFile.exists(SmbFile.java:1415) at com.company.collector.common.SmbFileWrapper.exists(SmbFileWrapper.java:56) at com.company.collector.datasource.dirwatcher.impl.DirectoryWatcher.checkDirectory(DirectoryWatcher.java:178) at com.company.collector.datasource.dirwatcher.impl.DirectoryWatcher.initializeHandler(DirectoryWatcher.java:166) at com.company.collector.datasource.dirwatcher.impl.DirectoryWatcher.start(DirectoryWatcher.java:108) at com.company.collector.datasource.dirwatcher.impl.DirectoryWatcher.run(DirectoryWatcher.java:86) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(UnknownSource) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(UnknownSource) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

    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

    Unknown user
    2 times, 11 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 month ago
    259 more bugmates