camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Burkard <>
Subject Camel marker files ".camelLock" not deleted
Date Mon, 13 Mar 2017 14:47:11 GMT
Hi Camel riders

I have a quite simple polling file consumer that runs fine on 2 instances.

.log("[FILEREADER " + routeId + "], file: ${in.header.CamelFileName}")
.setBody(method(bomProcessor, "removeBomIfPresent"))

The fileUri options are:
- initialDelay=[random-range]
- delay=[configurable]
- antFilterCaseSensitive=false
- antInclude=*.xml
- preMove=processing
- delete=true
- moveFailed=../error

I generate a random start delay to avoid both consumers running at the same
time. However sometimes they overlap and want to process the same file.

In this case I see normal processing in the logfile of one instance and an
error in the log of the other instance. So it works perfectly. With one
small flaw: the marker files of Camel (whatever.camelLock) are not deleted.
That makes the operation guys nervous.

Can I do something so that these marker files are deleted? Is this kind of
a misconfiguration of my file endpoint?

Thanks a lot

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message