[ https://issues.apache.org/jira/browse/HDFS-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201820#comment-14201820 ]
Steve Loughran commented on HDFS-7376: -------------------------------------- not seen any reports of this -yet- but it still seems worth doing. It's too late to do it for 2.6; targeting 2.7, which is java7+ only > Upgrade jsch lib to jsch-0.1.51 to avoid problems running on java7 > ------------------------------------------------------------------ > > Key: HDFS-7376 > URL: https://issues.apache.org/jira/browse/HDFS-7376 > Project: Hadoop HDFS > Issue Type: Bug > Components: build > Reporter: Johannes Zillmann > > We had an application sitting on top of Hadoop and got problems using jsch > once we switched to java 7. Got this exception: > {noformat} > com.jcraft.jsch.JSchException: verify: false > at com.jcraft.jsch.Session.connect(Session.java:330) > at com.jcraft.jsch.Session.connect(Session.java:183) > {noformat} > Upgrading to jsch-0.1.51 from jsch-0.1.49 fixed the issue for us, but then it > got in conflict with hadoop's jsch version (we fixed this for us by > jarjar'ing our jsch version). > So i think jsch got introduce by namenode HA (HDFS-1623). So you guys should > check if the ssh part is properly working for java7 or preventively upgrade > the jsch lib to jsch-0.1.51! > Some references to problems reported: > - > http://sourceforge.net/p/jsch/mailman/jsch-users/thread/loom.20131009t211650-...@post.gmane.org/ > - https://issues.apache.org/bugzilla/show_bug.cgi?id=53437 -- This message was sent by Atlassian JIRA (v6.3.4#6332)