OK - I will let you know when we've tested with setServerAliveInterval. Mind you, it will take a couple of months until we know (or at least believe) that we have fixed the problem since it occurs about once a  month today.


2012/10/17 Atsuhiko Yamanaka <ymnk@jcraft.com>

   +-From: Bengt Rodehav <bengt@rodehav.com> --
   |_Date: Wed, 17 Oct 2012 09:56:26 +0200 ____
   |But, how is it possible that the read() call can hang for several days?
   |Does Jsch use any default read timeout? If not, how can I configure it?
   |Finally I would hope that the TCPKeepAlive at the socket level would kick
   |in after a while and mark the other end as "dead" and then close
   |the socket.

If setServerAliveInterval() does not resolve the problem,
TCPKeepAlive will not. I just want to get a hint to find where is the problem.

Atsuhiko Yamanaka
SENDAI, MIYAGI 980-0014 Japan.
Tel +81-22-723-2150
Skype callto://jcraft/
Twitter: http://twitter.com/ymnk
Facebook: http://facebook.com/aymnk