Potential bug in sFTP (jSCH)?

[deepak_a]

Hi,

I am using Camel 2.12.0.
I have a route that establishes a sFTP connection.
I have set the route so that it will attempt to re-connect every 15 minutes
and then disconnect.
This is set up because the sFTP service provider has explicitly requested
not to keep connection open and poll at regular intervals. 

                <route id="emir_sftpDTCCToReform5" reform:name="Emir Messages 
from DTCC
SFTP5" reform:systemName="Emir Messages from DTCC SFTP5">                  
                        <from
uri=&quot;sftp://${emir.dtcc.sftp.user}@${emir.dtcc.sftp.url}///DTS4.DOWN.G5${emir.gtr.OriginatorId}?filter=#sftpFilter&amp;amp;disconnect=true&amp;amp;idempotent=true&amp;amp;idempotentRepository=#jpaStore&amp;amp;password=${emir.dtcc.sftp.password}&amp;amp;binary=true&amp;amp;delay=900000&amp;amp;stepwise=false&amp;amp;&lt;i>maximumReconnectAttempts=0"/>
            <setHeader headerName="messageType">
                <simple>SFTPDTCC</simple>
            </setHeader>                        

                        <to uri="jms:queue:queue.incomingEvents"/>
                </route> 


The connection works fine as expected but I see the following in the log
every time the route disconnects

[2014-06-24 18:57:25,300 Camel (camel) thread #133 -
sftp://F7DGTLRW@207.45.41.162:22///DTS4.DOWN.G5TLR] SftpConsumer                
  
INFO  Connecte
d and logged in to: sftp://F7DGTLRW@207.45.41.162:22
[2014-06-24 18:57:25,707 Camel (camel) thread #133 -
sftp://F7DGTLRW@207.45.41.162:22///DTS4.DOWN.G5TLR] SftpOperations              
  
INFO  JSCH ->
Disconnecting from 207.45.41.162 port 22
[2014-06-24 18:57:25,708 Connect thread 207.45.41.162 session]
SftpOperations                 INFO  JSCH -> Caught an exception, leaving
main loop due
 to socket closed



I am trying to set the log to debug level - but I am unable to change the
log level for jSCH component to get debug.

I have tried setting
log4j.logger.org.apache.camel.component.jsch=DEBUG
But this has no effect.

Has anyone else had this problem - I do not see this as a show stopper -
since the route reconnects as expected but I am concerned that there could
be stale ssh sessions left open.

Can some one advise on how to tackle this?


regards
D



--
View this message in context: 
http://camel.465427.n5.nabble.com/Potential-bug-in-sFTP-jSCH-tp5752764.html
Sent from the Camel - Users mailing list archive at Nabble.com.