org.tmatesoft.svn.core.SVNException

svn: Cannot connect to 'svn+ssh://<our server>.com': Sorry, this connection is 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.

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 web1010

  • svn: Cannot connect to 'svn+ssh://<our server>.com': Sorry, this connection is closed.
  • via nabble.com by Unknown author, 11 months ago
    svn: Cannot connect to 'svn+ssh://<our server>.com': Sorry, this connection is closed.
  • via Jenkins JIRA by tal, 11 months ago
    svn: Cannot connect to 'svn+ssh://...': Sorry, this connection is closed. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:63) at org.tmatesoft.svn.core.internal.io.svn.SVNGanymedConnector.open(SVNGanymedConnector.java:129)
  • Stack trace

    • org.tmatesoft.svn.core.SVNException: svn: Cannot connect to 'svn+ssh://<our server>.com': Sorry, this connection is closed. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:63) at org.tmatesoft.svn.core.internal.io.svn.SVNGanymedConnector.open(SVNGanymedConnector.java:129) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:60) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:970) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:140) at com.zutubi.pulse.scm.svn.SVNServer.getLatestRevision(SVNServer.java:545) at com.zutubi.pulse.scm.svn.SVNServer.reportChanges(SVNServer.java:353) at com.zutubi.pulse.scm.svn.SVNServer.getChanges(SVNServer.java:502) at com.zutubi.pulse.scm.svn.SVNServer.getRevisionsSince(SVNServer.java:508) at com.zutubi.pulse.model.DefaultScmManager.getLatestRevisionSince(DefaultScmManager.java:248) at com.zutubi.pulse.model.DefaultScmManager.process(DefaultScmManager.java:229) at com.zutubi.pulse.model.DefaultScmManager.access$000(DefaultScmManager.java:32) at com.zutubi.pulse.model.DefaultScmManager$1.run(DefaultScmManager.java:133) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.io.IOException: Sorry, this connection is closed. at ch.ethz.ssh2.transport.TransportManager.sendMessage(TransportManager.java:635) at ch.ethz.ssh2.channel.ChannelManager.openSessionChannel(ChannelManager.java:566) at ch.ethz.ssh2.Session.<init>(Session.java:39) at ch.ethz.ssh2.Connection.openSession(Connection.java:965) at org.tmatesoft.svn.core.internal.io.svn.SVNGanymedSession$SSHConnectionInfo.openSession(SVNGanymedSession.java:421) at org.tmatesoft.svn.core.internal.io.svn.SVNGanymedConnector.open(SVNGanymedConnector.java:89) ... 14 more Caused by: java.net.SocketException: Connection timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at ch.ethz.ssh2.crypto.cipher.CipherInputStream.fill_buffer(CipherInputStream.java:41) at ch.ethz.ssh2.crypto.cipher.CipherInputStream.internal_read(CipherInputStream.java:52) at ch.ethz.ssh2.crypto.cipher.CipherInputStream.getBlock(CipherInputStream.java:79) at ch.ethz.ssh2.crypto.cipher.CipherInputStream.read(CipherInputStream.java:108) at ch.ethz.ssh2.transport.TransportConnection.receiveMessage(TransportConnection.java:231) at ch.ethz.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:669) at ch.ethz.ssh2.transport.TransportManager$1.run(TransportManager.java:468) ... 1 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

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 11 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    314 more bugmates