The FileIdempotentRepositoryReadLockStrategy.acquireExclusiveReadLock method
guards against processing the same file twice.
So specification of the scheduler.triggerId is NOT required to ensure that
the file is only processed once in the cluster
--
View this message in context:
http://camel.465
Am using a camel file consumer within a cluster to poll files on a periodic
basis. I wish to ensure that a consumer will only poll files if it has an
exclusive read lock on them so using the
QuartzScheduledPollConsumerScheduler with a readLock=idempotent read lock
strategy backed by a JdbcMessageId
