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 41EF610D68 for ; Thu, 27 Mar 2014 03:41:26 +0000 (UTC) Received: (qmail 38246 invoked by uid 500); 27 Mar 2014 03:41:24 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 38037 invoked by uid 500); 27 Mar 2014 03:41:23 -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 Received: (qmail 38028 invoked by uid 99); 27 Mar 2014 03:41:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2014 03:41:23 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of paulc8712@gmail.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2014 03:41:18 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WT1BY-0004XE-37 for users@camel.apache.org; Wed, 26 Mar 2014 20:40:56 -0700 Date: Wed, 26 Mar 2014 20:40:56 -0700 (PDT) From: paulc8712 To: users@camel.apache.org Message-ID: <1395891656017-5749408.post@n5.nabble.com> Subject: File Consumer getting blocked MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi. I have a file consumer that intermittently gets 'blocked'. There is a file in the directory, and the route has 1 'inflight' message but it never clears. I typically also see a .lock file who's time-stamp does increase. It seems to me that it is waiting for the file write to be completed. My endpoint is configured as: file://{{filebase}}?moveFailed=.error&readLock=changed&readLockMinLength=0 I have also tried putting readLockCheckInterval=10000, and while it did seem to decrease the frequency of the 'block', it still does occur. Any suggestions to either help diagnose the problem, or some alterative techniques that I could try? Thanks, PC -- View this message in context: http://camel.465427.n5.nabble.com/File-Consumer-getting-blocked-tp5749408.html Sent from the Camel - Users mailing list archive at Nabble.com.