Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Jenkins JIRA by moshe010, 1 year ago
There was a problem while connecting to XXXXXXXXXXXXXXXXXXXXXXXXXX:22
via Jenkins JIRA by moshe010, 1 year ago
There was a problem while connecting to XXXXXXXXXXXXXXXXXXXXXXXXXX:22
via Stack Overflow by IAmYourFaja
, 2 years ago
There was a problem while connecting to myserver.example.com:22
via Stack Overflow by sradforth
, 2 years ago
There was a problem while connecting to 192.168.0.102:22
via stackexchange.com by Unknown author, 11 months ago
via Jenkins JIRA by fullung, 1 year ago
There was a problem while connecting to 172.16.63.206:22
java.io.IOException: The server sent a too long line.	at com.trilead.ssh2.transport.ClientServerHello.readLineRN(ClientServerHello.java:51)	at com.trilead.ssh2.transport.ClientServerHello.(ClientServerHello.java:68)	at com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:457)	at com.trilead.ssh2.Connection.connect(Connection.java:699)	at com.trilead.ssh2.Connection.connect(Connection.java:546)	at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:523)	at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:179)	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:184)	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)	at java.util.concurrent.FutureTask.run(Unknown Source)	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)	at java.lang.Thread.run(Unknown Source)