[CAMEL-5776] .camelLock is deleted by another camel instance

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.10.2
• Fix Version/s: 2.9.5, 2.10.3, 2.11.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Willem Jiang
• Reporter: David Larsson
• Created: 07/Nov/12 15:25
• Updated: 16/Nov/12 15:19
• Resolved: 16/Nov/12 15:19

Description

When camel file component tries to aquire a readLock, e.g. readLock=changed, and a camelLock already exists (aquired by another camel instance), the method MarkerFileExclusiveReadLockStrategy.acquireExclusiveReadLock fails (correct).

Then in GenericFileConsumer.processExchange, row 291 processStrategy.abort is called. That will delete the camelLock which another camel instance owns.

I don't know if abort should call exclusiveReadLockStrategy.releaseExclusiveReadLock() or if we have to remember if we own the lock or not.