Atsuhiko,
I am still working on the issue.
In the mean time you might want to patch jsch with this:
diff -ur jsch-0.1.31-m2-sources/com/jcraft/jsch/Session.java jsch-0.1.31
/src/com/jcraft/jsch/Session.java
--- jsch-0.1.31-m2-sources/com/jcraft/jsch/Session.java 2007-11-05 16:46:
09.689204300 +0100
+++ jsch-0.1.31/src/com/jcraft/jsch/Session.java 2007-10-29 20:28:
15.687500000 +0100
@@ -491,7 +491,7 @@
//e.printStackTrace();
if(e instanceof RuntimeException) throw (RuntimeException)e;
if(e instanceof JSchException) throw (JSchException)e;
- throw new JSchException("Session.connect: "+e);
+ throw new JSchException("Session.connect: "+e, e);
}
finally{
Util.bzero(this.password);
so that the cause isn't lost. I also suggest to review if there are other
places where JschException is created without a cause.
Thanks !
J
PS: using a log library might be good, especially as you say that ssh -X
helped you a lot :)
slf4j is a good alternative and can be disabled at deployment and runtime.
Log4j isn't bad either. Or Sun's.
Let me know if you are interested and need help with this.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
JSch-users mailing list
JSch-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users
