hudson.remoting.Channel$OrderlyShutdown: java.util.concurrent.TimeoutException: Ping started on 1341254668579 hasn't completed at 1341254908585

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 christian symmons, 1 year ago
java.util.concurrent.TimeoutException: Ping started on 1341254668579 hasn't completed at 1341254908585
via jenkins-ci.org by Unknown author, 11 months ago
java.util.concurrent.TimeoutException: Ping started on 1341254668579 hasn't completed at 1341254908585
via Jenkins JIRA by christian symmons, 1 year ago
java.util.concurrent.TimeoutException: Ping started on 1341254668579 hasn't completed at 1341254908585
via nabble.com by Unknown author, 2 years ago
java.util.concurrent.TimeoutException: Ping started on 1392852728137 hasn't completed at 1392852968137
via nabble.com by Unknown author, 2 years ago
java.util.concurrent.TimeoutException: Ping started on 1437416070507 hasn't completed at 1437416310507
hudson.remoting.Channel$OrderlyShutdown: java.util.concurrent.TimeoutException: Ping started on 1341254668579 hasn't completed at 1341254908585
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:818)
at hudson.remoting.Channel$1.handle(Channel.java:416)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.