camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Larsson (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5776) .camelLock is deleted by another camel instance
Date Thu, 08 Nov 2012 13:17:12 GMT


David Larsson commented on CAMEL-5776:

I noticed this when I created the lock file manually and had trace logging on. I saw that
camel deleted the lock file and then consumed the file in the next polling...

I think the test could be built like this:

1) Create a lock file (/files/test.camelLock)
2) Create a file (/files/test)
3) Start camel file consumer
4) Check that camel doesn't delete lock file when polling files directory (this fails for
camel 2.10.2 but works for camel 2.8.3)
5) Remove lock file
6) Make sure file is consumed on next polling

Regards David
> .camelLock is deleted by another camel instance
> -----------------------------------------------
>                 Key: CAMEL-5776
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.10.2
>            Reporter: David Larsson
>            Assignee: Willem Jiang
> 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:

View raw message