This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new 4a7d785 Regen
4a7d785 is described below
commit 4a7d785e54a902b2d1f6269d9edbe15e708ba8ea
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Dec 6 09:36:08 2018 +0100
Regen
---
components/camel-ftp/src/main/docs/ftp-component.adoc | 2 +-
components/camel-ftp/src/main/docs/ftps-component.adoc | 2 +-
components/camel-ftp/src/main/docs/sftp-component.adoc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/components/camel-ftp/src/main/docs/ftp-component.adoc
b/components/camel-ftp/src/main/docs/ftp-component.adoc
index 8f0127f..77628c4 100644
--- a/components/camel-ftp/src/main/docs/ftp-component.adoc
+++ b/components/camel-ftp/src/main/docs/ftp-component.adoc
@@ -189,7 +189,7 @@ with the following path and query parameters:
| *readLock* (lock) | Used by consumer, to only poll the files if it has
exclusive read-lock on the file (i.e. the file is not in-progress or being
written). Camel will wait until the file lock is granted. This option provides
the build in strategies: none - No read lock is in use markerFile - Camel
creates a marker file (fileName.camelLock) and then holds a lock on it. This
option is not available for the FTP component changed - Changed is using file
length/modification timestamp to det [...]
| *readLockCheckInterval* (lock) | Interval in millis for the read-lock, if
supported by the read lock. This interval is used for sleeping between attempts
to acquire the read lock. For example when using the changed read lock, you can
set a higher interval period to cater for slow writes. The default of 1 sec.
may be too fast if the producer is very slow writing the file. Notice: For FTP
the default readLockCheckInterval is 5000. The readLockTimeout value must be
higher than readLockChe [...]
| *readLockDeleteOrphanLock Files* (lock) | Whether or not read lock with
marker files should upon startup delete any orphan read lock files, which may
have been left on the file system, if Camel was not properly shutdown (such as
a JVM crash). If turning this option to false then any orphaned lock file will
cause Camel to not attempt to pickup that file, this could also be due another
node is concurrently reading files from the same shared directory. | true |
boolean
-| *readLockLoggingLevel* (lock) | Logging level used when a read lock could
not be acquired. By default a WARN is logged. You can change this level, for
example to OFF to not have any logging. This option is only applicable for
readLock of types: changed, fileLock, idempotent, idempotent-changed,
idempotent-rename, rename. | DEBUG | LoggingLevel
+| *readLockLoggingLevel* (lock) | Logging level used when a read lock could
not be acquired. By default a DEBUG is logged. You can change this level, for
example to OFF to not have any logging. This option is only applicable for
readLock of types: changed, fileLock, idempotent, idempotent-changed,
idempotent-rename, rename. | DEBUG | LoggingLevel
| *readLockMarkerFile* (lock) | Whether to use marker file with the changed,
rename, or exclusive read lock types. By default a marker file is used as well
to guard against other processes picking up the same files. This behavior can
be turned off by setting this option to false. For example if you do not want
to write marker files to the file systems by the Camel application. | true |
boolean
| *readLockMinAge* (lock) | This option is applied only for readLock=changed.
It allows to specify a minimum age the file must be before attempting to
acquire the read lock. For example use readLockMinAge=300s to require the file
is at last 5 minutes old. This can speedup the changed read lock as it will
only attempt to acquire files which are at least that given age. | 0 | long
| *readLockMinLength* (lock) | This option is applied only for
readLock=changed. It allows you to configure a minimum file length. By default
Camel expects the file to contain data, and thus the default value is 1. You
can set this option to zero, to allow consuming zero-length files. | 1 | long
diff --git a/components/camel-ftp/src/main/docs/ftps-component.adoc
b/components/camel-ftp/src/main/docs/ftps-component.adoc
index 5d2533c..4bb1b2d 100644
--- a/components/camel-ftp/src/main/docs/ftps-component.adoc
+++ b/components/camel-ftp/src/main/docs/ftps-component.adoc
@@ -153,7 +153,7 @@ with the following path and query parameters:
| *readLockIdempotentRelease AsyncPoolSize* (lock) | The number of threads in
the scheduled thread pool when using asynchronous release tasks. Using a
default of 1 core threads should be sufficient in almost all use-cases, only
set this to a higher value if either updating the idempotent repository is
slow, or there are a lot of files to process. This option is not in-use if you
use a shared thread pool by configuring the
readLockIdempotentReleaseExecutorService option. See more details [...]
| *readLockIdempotentRelease Delay* (lock) | Whether to delay the release task
for a period of millis. This can be used to delay the release tasks to expand
the window when a file is regarded as read-locked, in an active/active cluster
scenario with a shared idempotent repository, to ensure other nodes cannot
potentially scan and acquire the same file, due to race-conditions. By
expanding the time-window of the release tasks helps prevents these situations.
Note delaying is only needed i [...]
| *readLockIdempotentRelease ExecutorService* (lock) | To use a custom and
shared thread pool for asynchronous release tasks. See more details at the
readLockIdempotentReleaseDelay option. | | ScheduledExecutor Service
-| *readLockLoggingLevel* (lock) | Logging level used when a read lock could
not be acquired. By default a WARN is logged. You can change this level, for
example to OFF to not have any logging. This option is only applicable for
readLock of types: changed, fileLock, idempotent, idempotent-changed,
idempotent-rename, rename. | DEBUG | LoggingLevel
+| *readLockLoggingLevel* (lock) | Logging level used when a read lock could
not be acquired. By default a DEBUG is logged. You can change this level, for
example to OFF to not have any logging. This option is only applicable for
readLock of types: changed, fileLock, idempotent, idempotent-changed,
idempotent-rename, rename. | DEBUG | LoggingLevel
| *readLockMarkerFile* (lock) | Whether to use marker file with the changed,
rename, or exclusive read lock types. By default a marker file is used as well
to guard against other processes picking up the same files. This behavior can
be turned off by setting this option to false. For example if you do not want
to write marker files to the file systems by the Camel application. | true |
boolean
| *readLockMinAge* (lock) | This option is applied only for readLock=changed.
It allows to specify a minimum age the file must be before attempting to
acquire the read lock. For example use readLockMinAge=300s to require the file
is at last 5 minutes old. This can speedup the changed read lock as it will
only attempt to acquire files which are at least that given age. | 0 | long
| *readLockMinLength* (lock) | This option is applied only for
readLock=changed. It allows you to configure a minimum file length. By default
Camel expects the file to contain data, and thus the default value is 1. You
can set this option to zero, to allow consuming zero-length files. | 1 | long
diff --git a/components/camel-ftp/src/main/docs/sftp-component.adoc
b/components/camel-ftp/src/main/docs/sftp-component.adoc
index e2591e5..08e3dc8 100644
--- a/components/camel-ftp/src/main/docs/sftp-component.adoc
+++ b/components/camel-ftp/src/main/docs/sftp-component.adoc
@@ -137,7 +137,7 @@ with the following path and query parameters:
| *readLockIdempotentRelease AsyncPoolSize* (lock) | The number of threads in
the scheduled thread pool when using asynchronous release tasks. Using a
default of 1 core threads should be sufficient in almost all use-cases, only
set this to a higher value if either updating the idempotent repository is
slow, or there are a lot of files to process. This option is not in-use if you
use a shared thread pool by configuring the
readLockIdempotentReleaseExecutorService option. See more details [...]
| *readLockIdempotentRelease Delay* (lock) | Whether to delay the release task
for a period of millis. This can be used to delay the release tasks to expand
the window when a file is regarded as read-locked, in an active/active cluster
scenario with a shared idempotent repository, to ensure other nodes cannot
potentially scan and acquire the same file, due to race-conditions. By
expanding the time-window of the release tasks helps prevents these situations.
Note delaying is only needed i [...]
| *readLockIdempotentRelease ExecutorService* (lock) | To use a custom and
shared thread pool for asynchronous release tasks. See more details at the
readLockIdempotentReleaseDelay option. | | ScheduledExecutor Service
-| *readLockLoggingLevel* (lock) | Logging level used when a read lock could
not be acquired. By default a WARN is logged. You can change this level, for
example to OFF to not have any logging. This option is only applicable for
readLock of types: changed, fileLock, idempotent, idempotent-changed,
idempotent-rename, rename. | DEBUG | LoggingLevel
+| *readLockLoggingLevel* (lock) | Logging level used when a read lock could
not be acquired. By default a DEBUG is logged. You can change this level, for
example to OFF to not have any logging. This option is only applicable for
readLock of types: changed, fileLock, idempotent, idempotent-changed,
idempotent-rename, rename. | DEBUG | LoggingLevel
| *readLockMarkerFile* (lock) | Whether to use marker file with the changed,
rename, or exclusive read lock types. By default a marker file is used as well
to guard against other processes picking up the same files. This behavior can
be turned off by setting this option to false. For example if you do not want
to write marker files to the file systems by the Camel application. | true |
boolean
| *readLockMinAge* (lock) | This option is applied only for readLock=changed.
It allows to specify a minimum age the file must be before attempting to
acquire the read lock. For example use readLockMinAge=300s to require the file
is at last 5 minutes old. This can speedup the changed read lock as it will
only attempt to acquire files which are at least that given age. | 0 | long
| *readLockMinLength* (lock) | This option is applied only for
readLock=changed. It allows you to configure a minimum file length. By default
Camel expects the file to contain data, and thus the default value is 1. You
can set this option to zero, to allow consuming zero-length files. | 1 | long
