Hi,
+-From: Haidong Zhu <[email protected]> --
|_Date: Thu, 6 May 2010 16:19:05 +0800 ________
|
|The jsch version is 0.1.42
|Below is part of the jstack output:
|10 "Connect thread 192.168.1.116 session" prio=5 tid=0x02946000
nid=0xb1327000 runnable [0xb1326000]
| 11 java.lang.Thread.State: RUNNABLE
| 12 at java.net.SocketInputStream.socketRead0(Native Method)
| 13 at java.net.SocketInputStream.read(SocketInputStream.java:129)
| 14 at com.jcraft.jsch.IO.getByte(IO.java:82)
| 15 at com.jcraft.jsch.Session.read(Session.java:811)
| 16 at com.jcraft.jsch.Session.run(Session.java:1195)
| 17 at java.lang.Thread.run(Thread.java:637)
I could not reproduce such a problem on ScpTo.java without System.exit(0).
The reason for System.exit(0) in ScpTo.java example is that
it was not terminated because of the Swing(or AWT?) UI thread on
the previous JDK, but it seems it is not required anymore on
Sun's Java6 environment.
Sincerely,
--
Atsuhiko Yamanaka
JCraft,Inc.
1-14-20 HONCHO AOBA-KU,
SENDAI, MIYAGI 980-0014 Japan.
Tel +81-22-723-2150
+1-415-578-3454
Skype callto://jcraft/
------------------------------------------------------------------------------
_______________________________________________
JSch-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jsch-users
