Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <1808841463.1251092150208.JavaMail.jira@brutus>
Date: Sun, 23 Aug 2009 22:35:50 -0700 (PDT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-1927) FileConsumer preMove setting causes
 filename to be left in in progress repository.
In-Reply-To: <523661123.1250922155731.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-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53733#action_53733 ] 

Claus Ibsen commented on CAMEL-1927:
------------------------------------

The issue is in related when you use {{preMove}} and change the actual name of the file such as prepending {{work-}} or the likes to the file name.
However if you use {{preMove}} to move the file to another directory then the name is correctly removed from the repo.


> FileConsumer preMove setting causes filename to be left in in progress repository.
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-1927
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1927
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.0-M3
>            Reporter: Alexander Lee
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>
> If the FileConsumer preMove setting is used, then files are picked up the first time only, as the original file name is added to the in progress repository, whereas the new file name is removed from the in progress repository (though nothing is actually removed as the new file name is not in the in progress repository).
> This causes a few problems:
> i) If the maxMessagePerPoll is used, then messages not processed the first time are never picked up again.
> ii) If the intention is to reprocess the same file, or a new file with the same name, then it will never be picked up again after the first time.
> iii)  As the wrong file names are removed from the in progress repository, it results in a slow memory leak in the in progress repository.

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