Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <1123241665.1244362970688.JavaMail.jira@brutus>
Date: Sun, 7 Jun 2009 01:22:50 -0700 (PDT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-1670) thread() and File Components
In-Reply-To: <1447642817.1244156270584.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/CAMEL-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52100#action_52100 ] 

Claus Ibsen commented on CAMEL-1670:
------------------------------------

This is a first cut for a fix. It resolves the issue for the markerFile lock (the default one).

But we are considering a more generic solution for registering in progress exchanges. For instance there is a ticket about idempotent consumer EIP pattern that could also benefit from this.

trunk: 782345.

> thread() and File Components
> ----------------------------
>
>                 Key: CAMEL-1670
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1670
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0-M1
>         Environment: Microsoft Windows XP
>            Reporter: Joe Gottman
>            Assignee: Claus Ibsen
>
> I just experimented with adding calls to thread(10) to my route to make it multithreaded.  This definitely speeds up by route, but it keeps throwing java.nio.channels.OverlappingFileLockException  errors and leaving lock files behind it.  The start of my route looks like
>  
> from("file:\\startDirectory?move=endDirectory")
> .threads(10)
> .bean("myBean", "myMethod")
> Afterwards, my route ran successfully but an OverlappingFileLockException was thrown for every file that was read and all the lock files were left in my source directory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.