RE: [camel-ftp] Can't catch Invalid SFTP port exception

2016-10-18 Thread Goyal, Arpit
: [camel-ftp] Can't catch Invalid SFTP port exception Try with Camel 2.18.0 release. We may have fixed something about this. There is a vague memory of mine looking into and fixing something with consumer template and bridge. On Sun, Oct 16, 2016 at 9:54 PM, Goyal, Arpit <arpit.go...@sap.com>

Re: [camel-ftp] Can't catch Invalid SFTP port exception

2016-10-18 Thread Claus Ibsen
Try with Camel 2.18.0 release. We may have fixed something about this. There is a vague memory of mine looking into and fixing something with consumer template and bridge. On Sun, Oct 16, 2016 at 9:54 PM, Goyal, Arpit wrote: > I am trying to handle all the exception use

RE: [camel-ftp] Can't catch Invalid SFTP port exception

2016-10-18 Thread Goyal, Arpit
Sent: Tuesday, October 18, 2016 8:10 AM To: users@camel.apache.org Subject: Re: [camel-ftp] Can't catch Invalid SFTP port exception Have you tried enabling the bridge error handler feature (consumer.bridgeErrorHandler)? http://camel.apache.org/file2.html <http://camel.apache.org/file2.html>

Re: [camel-ftp] Can't catch Invalid SFTP port exception

2016-10-18 Thread Quinn Stevenson
Have you tried enabling the bridge error handler feature (consumer.bridgeErrorHandler)? http://camel.apache.org/file2.html > On Oct 18, 2016, at 7:33 AM, Goyal, Arpit wrote: > > Anyone having idea about what's wrong here? > > Sent

Re: [camel-ftp] Can't catch Invalid SFTP port exception

2016-10-18 Thread Goyal, Arpit
Anyone having idea about what's wrong here? Sent from my iPhone > On Oct 16, 2016, at 12:55 PM, Goyal, Arpit wrote: > > I am trying to handle all the exception use cases of SFTP for logging > purposes. In case user has given invalid Port address for sftp server even >

[camel-ftp] Can't catch Invalid SFTP port exception

2016-10-16 Thread Goyal, Arpit
I am trying to handle all the exception use cases of SFTP for logging purposes. In case user has given invalid Port address for sftp server even when using pollStrategy attribute -> 1) We are not able to get the exception back in the code. 2) Exchange comes back null. 3) Associated below code