-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting "Key exchange was not finished, connection is closed" exception #140
Comments
I'm not sure we can help you, this is an old version of the JNC client, the Ganymed SSH library is unsupported, again, can you migrate to a newer version? |
Thanks for info. We are using maven project so please check below new JNC gradle info converted to pom.xml to support maven based. Is this file is fine or anything needs to be added?
|
This appears to be a POM file for building the JNC library, I would not expect you need that; I believe the "only" thing you need to do is to add a link to our Maven repository and JNC dependency declaration to your project's POM file. |
For the sake of completeness, you need to have something like this in your POM (or POMs):
That alone does not deal with generating Java classes from YANG modules using the pyang plugin, I assume you already have that somehow. |
Hi Team,
Recently upgraded our application from Java 8 to Java 17. And we have compiled the JNC and ganymed module as well. But when will bringup our springboot application will call device connect but we are seeing below exception:
This was not there when application running in Java8. Can any one help on this.
[main] Key exchange was not finished, connection is closed.
java.io.IOException: Key exchange was not finished, connection is closed.
at ch.ethz.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:75) ~[ganymed-ssh2-262.jar!/:262]
at ch.ethz.ssh2.transport.TransportManager.getConnectionInfo(TransportManager.java:169) ~[ganymed-ssh2-262.jar!/:262]
at ch.ethz.ssh2.Connection.connect(Connection.java:759) ~[ganymed-ssh2-262.jar!/:262]
at com.tailf.jnc.SSHConnection.(Unknown Source) ~[jnc-1.0.jar!/:?]
at com.tailf.jnc.Device.connect(Unknown Source) ~[jnc-1.0.jar!/:?]
at com.tailf.jnc.Device.connect(Unknown Source) ~[jnc-1.0.jar!/:?]
The text was updated successfully, but these errors were encountered: