Yes, definitely. I will be using the documentation on Github in the future from now on, thanks.
Jaap On Thu, Jan 12, 2017 at 12:44 PM, Andrea Cosentino <ancosen1...@yahoo.com.invalid> wrote: > By the way I updated the confluence page too. > > Anyway we need to emphasize the new documentation is directly on github and > in future we'll use it for generating a complete site. > -- > Andrea Cosentino > ---------------------------------- > Apache Camel PMC Member > Apache Karaf Committer > Apache Servicemix Committer > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > On Thursday, January 12, 2017 12:40 PM, Claus Ibsen <claus.ib...@gmail.com> > wrote: > Use the documentation at github, its up to date with option and their > default values. > https://github.com/apache/camel/tree/master/components#components > > > On Thu, Jan 12, 2017 at 12:29 PM, Jaap Spiering <jaapspier...@gmail.com> > wrote: >> Hi Andrea, >> >> I know, but I am not asking about Fuse issues here, this is only a >> question about a possible error in the Camel documentation. >> >> regards, >> >> Jaap >> >> On Thu, Jan 12, 2017 at 11:21 AM, Andrea Cosentino >> <ancosen1...@yahoo.com.invalid> wrote: >>> For JBoss Fuse problem you'll need to ask to RH support and take a look at >>> the Fuse Camel documentation. >>> -- >>> Andrea Cosentino >>> ---------------------------------- >>> Apache Camel PMC Member >>> Apache Karaf Committer >>> Apache Servicemix Committer >>> Email: ancosen1...@yahoo.com >>> Twitter: @oscerd2 >>> Github: oscerd >>> >>> >>> >>> On Thursday, January 12, 2017 11:18 AM, Jaap Spiering >>> <jaapspier...@gmail.com> wrote: >>> Hi, >>> >>> we have recently been experiencing some Camel routes taking quite a >>> long time to complete with a visible five-minute delay in >>> communicating with an FTP endpoint. So I did some investigation and it >>> looks like this could be a socket timeout (which is new to us, we just >>> moved from 2.15 to 2.17 with Fuse 6.3). However, in the documentation >>> at >>> >>> http://camel.apache.org/ftp.html >>> >>> it says about the soTimeout: >>> >>> soTimeout null / 30000 >>> >>> FTP and FTPS Only: Camel 2.4: Is the SocketOptions.SO_TIMEOUT value in >>> millis. A good idea is to configure this to a value such as 300000 (5 >>> minutes) to not hang a connection. On SFTP this option is set as >>> timeout on the JSCH Session instance. >>> >>> Also SFTP from Camel 2.14.3/2.15.3/2.16 onwards. >>> >>> From Camel 2.16 onwards the default is 30000 (30 sec). >>> >>> While in the code (RemoteFileConfiguration) the default value of >>> soTimeout is set to 300000 (5 minutes) instead of 30000 (30 seconds). >>> >>> https://issues.apache.org/jira/secure/attachment/12736108/0001-CAMEL-8818-Set-default-for-SO_TIMEOUT-in-camel-ftp.patch >>> >>> So it looks like this could be a documentation issue and the suggested >>> value is actually the default value. Or am I missing something here? >>> >>> regards, >>> >>> Jaap > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
