Claus Ibsen-2 wrote > Use stop instead of suspend. I know that stopping the route does shut down the endpoints. But we changed to suspend/resume a month ago because we noticed that stop/restart leaks threads in GlassFish. If I did stop the route I would have to remove and recreate it each time Quartz fires. This would also knock down my whole approach of initially setting up routes on application startup.
At the moment I'm looking into endpoint options, something like: serverAliveInterval 900 serverAliveCountMax 0 This idea was inspired by http://serverfault.com/a/450916 But this doesn't seem to work neither. JSCH goes nuts and disconnects right before logging in and "SSH_MSG_KEXDH_INIT sent" should get logged. Regards, mdo. -- View this message in context: http://camel.465427.n5.nabble.com/SFTP-disconnect-on-route-suspend-tp5734742p5734744.html Sent from the Camel - Users mailing list archive at Nabble.com.
