[
https://issues.apache.org/jira/browse/CAMEL-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-5776.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.11.0
2.10.3
2.9.5
Applied the patch into trunk, camel-2.10.x and camel-2.9.x branches.
> .camelLock is deleted by another camel instance
> -----------------------------------------------
>
> Key: CAMEL-5776
> URL: https://issues.apache.org/jira/browse/CAMEL-5776
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.10.2
> Reporter: David Larsson
> Assignee: Willem Jiang
> Fix For: 2.9.5, 2.10.3, 2.11.0
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
