timeout in wating for rekeying process.

  • Jon Gorrono

    Jon Gorrono - 2014-05-21

    I have looked thru the code and I see that this occurs if the timeout passed into connect() is exceeded while negotiating... but what it confounding to me is that this message sometimes occurs immediately. My timeout is a static value in the same class and so cannot be null and it is set to 20000.

    jsch.addIdentity((String)settings.get(SSHTunnel.KEY_IDFILE), "");
    session = jsch.getSession((String)settings.get(SSHTunnel.KEY_REMOTEACCOUNT), (String)settings.get(SSHTunnel.KEY_REMOTEHOST));

    Last edit: Jon Gorrono 2014-05-21
    • Jon Gorrono

      Jon Gorrono - 2014-06-09

      More supporting information....

       line 0: private static int TIME_WAIT = 20000;
       line 1: l.debug("starting connection @ " + System.currentTimeMillis());
       line 2: session.connect(TIME_WAIT);
       line 3 l.debug("starting tunnel @ " + System.currentTimeMillis());
      log output:
      2014-06-06 19:59:13 DEBUG SSHTunnel$Tunnel:125 - starting connection @ 1402109953613
      2014-06-06 19:59:13 ERROR SSHTunnel$Tunnel:341 - timeout in wating for rekeying process.
      2014-06-06 19:59:13 INFO  SSHTunnel$Tunnel:197 - tunnel will remain open for 180 seconds
      2014-06-06 19:59:13 INFO  SSHTunnel$Tunnel:197 - Exiting SSH Tunnel thread - Thread[Thread-29,7,main]

      ... line 3 is never reached after the exception and the logoutput from line 1 is in the same second as the log output just before the connection attempt


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks