Hello, I would like to understand this strange behavior with my route starting with a file polling consumer :
I have sometimes two .camelLock remaining and some files waiting (blocked) while some new files are processed with success. These files blocked remain blocked until I delete manually the .camelLock file(s) extract of my property file : file2docb.consumerPolicy.delay=*1S* file2docb.consumerPolicy.maxMessagesPerPoll=*1* Below my routes with the starting point in bold: from("direct:file2docb.statusStartFlowNotifier") .throttle(1) .beanRef("gedStatusFlowNotifier", "start") .setHeader( "subject", simple(GedConstants.START_WORKFLOW + " [${header.setName}]")) .to("{{file2docb.smtpBusiness}}"); *from(* "file:{{file2docb.inboxDir.online}}?moveFailed=.error&include=.*\\.info&processStrategy=#processFileStrategy&initialDelay=10S&delay={{file2docb.consumerPolicy.delay}}&maxMessagesPerPoll={{file2docb.consumerPolicy.maxMessagesPerPoll}}") .routeId("file2docb.inBoxDir.online") .setHeader("isOnline", constant(true)) .setHeader("targetFrom", constant("file2docbridge-online")) .to("direct:file2docb.moveFiles4Docbridge"); from("direct:file2docb.moveFiles4Docbridge") .setHeader(GedConstants.FLOW_NAME, constant("FileToDocbridge")) .onCompletion() .onFailureOnly() .to("direct:file2docb.file2docbException") .end() .choice() .when() .method(BEAN_REF_FILE2DOCB_CAMEL_FACADE, "mustTriggerStatusStartFlowNotifier") .wireTap("direct:file2docb.statusStartFlowNotifier") .end() .beanRef(BEAN_REF_FILE2DOCB_CAMEL_FACADE, "moveFiles4Docbridge") .to("activemq:file2docb.callDocBridge"); Thanks in advance for your help Regards J-M -- View this message in context: http://camel.465427.n5.nabble.com/strange-file-polling-consumer-blocking-tp5602981p5602981.html Sent from the Camel - Users mailing list archive at Nabble.com.