Delete orphan camel lockfile

[Matteo Cusmai]

Hi all,
I am using file component with camel version 2.19.0 and I am experiencing a
strange behavior.

My endpoint is processing zip file so I have used include=.*.zip, is it
rigth?

If so, when I stop my application (I have a web app that runs on tomcat 8)
I have both the filename.zip and filename.zip.camelLock on processing
folder.

When I start again tomcat the web app is locked on that camelLock file.
After debug the camel code, in particular
MarkerFileExclusiveReadLockStrategy I think that there is a possible bug
in deleteLockFiles method. Since filename.zip.camelLock is not accepted the
next section

 if (file.getName().endsWith(FileComponent.DEFAULT_LOCK_FILE_POSTFIX)) {
                LOG.warn("Deleting orphaned lock file: " + file);
                FileUtil.deleteFile(file);
            } else if (recursive && file.isDirectory()) {
                deleteLockFiles(file, true, endpointPath, filter,
antFilter, excludePattern, includePattern);
            }

is skipped.

Could you help me to understand?

Thanks,

Matteo Cusmai