Before enabling setServerAlive on the production server I tested it locally
(using Serv-U as sftp server) to see that it actually will work. I set the
Camel option (for the sftp component) *serverAliveInterval* to 10. I poll
for files every 30 seconds. When I do this, it seems Jsch can no longer
connect to the server. I get the following exception:
*2012-10-17 14:29:50,350 | DEBUG | sample/sftp2file | SftpConsumer
| t.file.remote.RemoteFileConsumer 126 | Could not connect to:
Endpoint[sftp://user@localhost/sample/sftp2file?delay=30000&delete=true&disconnect=true&include=(?i).*(?%3C!%5C.TMP)&password=******&serverAliveInterval=10&stepwise=false].
Will try to recover.*
*org.apache.camel.component.file.GenericFileOperationFailedException:
Cannot connect to sftp://user@localhost:22*
* at
org.apache.camel.component.file.remote.SftpOperations.connect(SftpOperations.java:121)[123:org.apache.camel.camel-ftp:2.9.1]
*
* at
org.apache.camel.component.file.remote.RemoteFileConsumer.connectIfNecessary(RemoteFileConsumer.java:144)[123:org.apache.camel.camel-ftp:2.9.1]
*
* at
org.apache.camel.component.file.remote.RemoteFileConsumer.recoverableConnectIfNecessary(RemoteFileConsumer.java:123)[123:org.apache.camel.camel-ftp:2.9.1]
*
* at
org.apache.camel.component.file.remote.RemoteFileConsumer.prePollCheck(RemoteFileConsumer.java:56)[123:org.apache.camel.camel-ftp:2.9.1]
*
* at
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:89)[110:org.apache.camel.camel-core:2.9.1]
*
* at
org.apache.camel.impl.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:140)[110:org.apache.camel.camel-core:2.9.1]
*
* at
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:92)[110:org.apache.camel.camel-core:2.9.1]
*
* at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)[:1.6.0_25]
*
* at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)[:1.6.0_25]
*
* at
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)[:1.6.0_25]*
* at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)[:1.6.0_25]
*
* at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)[:1.6.0_25]
*
* at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)[:1.6.0_25]
*
* at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)[:1.6.0_25]
*
* at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)[:1.6.0_25]
*
* at java.lang.Thread.run(Thread.java:662)[:1.6.0_25]*
*Caused by: com.jcraft.jsch.JSchException: timeout in wating for rekeying
process.*
* at
com.jcraft.jsch.Session.write(Session.java:1192)[122:org.apache.servicemix.bundles.jsch:0.1.44.2]
*
* at
com.jcraft.jsch.DHG1.init(DHG1.java:127)[122:org.apache.servicemix.bundles.jsch:0.1.44.2]
*
* at
com.jcraft.jsch.Session.receive_kexinit(Session.java:547)[122:org.apache.servicemix.bundles.jsch:0.1.44.2]
*
* at
com.jcraft.jsch.Session.connect(Session.java:291)[122:org.apache.servicemix.bundles.jsch:0.1.44.2]
*
* at
org.apache.camel.component.file.remote.SftpOperations.connect(SftpOperations.java:93)[123:org.apache.camel.camel-ftp:2.9.1]
*
* ... 15 more*
The polling now stops and the files are not retrieved. Am I doing something
wrong here? What is the "rekeying process"?
Thanks,
/Bengt
2012/10/17 Bengt Rodehav <be...@rodehav.com>
> 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.
>
> /Bengt
>
>
> 2012/10/17 Atsuhiko Yamanaka <y...@jcraft.com>
>
>> Hi,
>>
>> +-From: Bengt Rodehav <be...@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.
>>
>>
>> Sincerely,
>> --
>> Atsuhiko Yamanaka
>> JCraft,Inc.
>> 1-14-20 HONCHO AOBA-KU,
>> SENDAI, MIYAGI 980-0014 Japan.
>> Tel +81-22-723-2150
>> Skype callto://jcraft/
>> Twitter: http://twitter.com/ymnk
>> Facebook: http://facebook.com/aymnk
>>
>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
JSch-users mailing list
JSch-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users
