Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7CBC810D16 for ; Thu, 3 Apr 2014 18:31:38 +0000 (UTC) Received: (qmail 42629 invoked by uid 500); 3 Apr 2014 18:31:37 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 42410 invoked by uid 500); 3 Apr 2014 18:31:36 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Delivered-To: moderator for users@camel.apache.org Received: (qmail 49047 invoked by uid 99); 3 Apr 2014 17:50:26 -0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Date: Thu, 3 Apr 2014 10:49:58 -0700 (PDT) From: Vinu Raj To: users@camel.apache.org Message-ID: <1396547398743-5749736.post@n5.nabble.com> Subject: File processing stops on bean invocation at times MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I have a simple route as following from("file:{{input.dir}}?sortBy=file:name&include=.*.data&move={{done.dir}}&delay={{poll.delay}}") .id("FileConsumer") .log("Processing file ${file:name}") .beanRef("FileBinder","bind") .beanRef("PU","execute") .log("Completed processing ${file:name}") .end(); Running Apache Camel 2.13.1 in Apache Karaf 3.0.0. I have around 100 files in the input directory. Camel processes 5-6 files initially and then the second bean invocation doesn't happen and the file processing stops at that point with no exceptions. I have another Camel route which is using quatrz2 cron like scheduler producing these files in {{input.dir}}. When ever there is an invocation from quartz scheduler in between the above mentioned route, the issue happens. What is going wrong here ? The camel trace MethodInfo.java:276 | >>>> invoking is not appearing for the second bean invocation. -- View this message in context: http://camel.465427.n5.nabble.com/File-processing-stops-on-bean-invocation-at-times-tp5749736.html Sent from the Camel - Users mailing list archive at Nabble.com.