Hi,
+-From: y...@jcraft.com (Atsuhiko Yamanaka) --
|_Date: Tue, 16 Jun 2009 10:54:45 +0900 ______
|
| +-From: Pan Li <pa...@prominic.net> ------
| |_Date: Mon, 15 Jun 2009 17:51:04 +0800 __
| |
| |This is output of jstack
| |The full output it quite long, this host (229) is one of the stuck
| | hosts.
| |So I think this is what you need.
| |Once it is stuck, output of jstack always looks like this,
| |it seems that it is always running Session.java:1159
|
|To get hints to reproduce that problem, I'm interested in stack traces
|from other threads. It will be long and other members on this ML list
|will not be interested in, so may I ask you to send it to me directly?
Thanks to the stack traces, the dead lock problem had been found and has
been fixed in jsch 0.1.42.
That dead lock may occur in making exec request during re-keying process.
According to RFC4344, rekey will be done after receiving 2^32 packets
since the last re-keying operation. To make this dead lock, you have to
make rexec during re-keying(before end of re-keying process),
so it is really rare to encounter this problem.
Many thanks for PanLi at Prominic dot NET and www.prominic.net,
US based hosting company. Without their testing JSch with
hundreds of hosts and their bug reports, this problem was not fixed.
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/
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
JSch-users mailing list
JSch-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users
