[CAMEL-8387] File consumer fails to acquire lock if readLockTimeout >= readLockCheckInterval

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.14.1
• Fix Version/s: 2.15.0
• Component/s: camel-core
• Estimated Complexity: Novice
• Assignee: Claus Ibsen
• Reporter: Christoffer Eide
• Created: 21/Feb/15 17:39
• Updated: 22/Feb/15 12:35
• Resolved: 22/Feb/15 09:50

Description

If the readLockCheckInterval is greater than or equal to readLockTimeout when using readLock=changed, the consumer never picks up any files.

So this URI will triggers the behaviour:
file:some-folder?readLock=changed&readLockCheckInterval=1000&readLockTimeout=500

The problem is that FileChangedExclusiveReadLockStrategy only takes readLockTimeout into account.

1. FileChangedExclusiveReadLockStrategy get the last modified and size of the file.
2. It sleeps for the duration configured in readLockCheckInterval
3. Now the timeout configured in readLockTimeout is exceeded, so FileChangedExclusiveReadLockStrategy logs "Cannot acquire read lock within.." and returns false