You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Farhad Dehghani (JIRA)" <ji...@apache.org> on 2010/04/27 11:37:26 UTC
[jira] Created: (CAMEL-2678) Removing entries from
FileIdempotentRepository don't get persisted
Removing entries from FileIdempotentRepository don't get persisted
------------------------------------------------------------------
Key: CAMEL-2678
URL: https://issues.apache.org/activemq/browse/CAMEL-2678
Project: Apache Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.2.0, 2.1.0, 2.0.0
Environment: JDK 1.5 & 1.6 / JBoss 4.2 / Camel 2.1.0 & 2.2.0
Reporter: Farhad Dehghani
Priority: Minor
Removing an entry (file name) programatically from a file idempotent repository has only effect on the cache and does not get persisted on the file repository.
There are some situations in which one may need to rerun a file through a workflow and it makes neccessary to remove the file from the idempotent repository. A specific problem arises when upon a server restart, the file is not picked up by the workflow because the remove was not persisted/spooled on the disk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-2678) Removing entries from
FileIdempotentRepository don't get persisted
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-2678.
--------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
trunk: 938828.
> Removing entries from FileIdempotentRepository don't get persisted
> ------------------------------------------------------------------
>
> Key: CAMEL-2678
> URL: https://issues.apache.org/activemq/browse/CAMEL-2678
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0.0, 2.1.0, 2.2.0
> Environment: JDK 1.5 & 1.6 / JBoss 4.2 / Camel 2.1.0 & 2.2.0
> Reporter: Farhad Dehghani
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.3.0
>
>
> Removing an entry (file name) programatically from a file idempotent repository has only effect on the cache and does not get persisted on the file repository.
> There are some situations in which one may need to rerun a file through a workflow and it makes neccessary to remove the file from the idempotent repository. A specific problem arises when upon a server restart, the file is not picked up by the workflow because the remove was not persisted/spooled on the disk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CAMEL-2678) Removing entries from
FileIdempotentRepository don't get persisted
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-2678:
----------------------------------
Assignee: Claus Ibsen
> Removing entries from FileIdempotentRepository don't get persisted
> ------------------------------------------------------------------
>
> Key: CAMEL-2678
> URL: https://issues.apache.org/activemq/browse/CAMEL-2678
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0.0, 2.1.0, 2.2.0
> Environment: JDK 1.5 & 1.6 / JBoss 4.2 / Camel 2.1.0 & 2.2.0
> Reporter: Farhad Dehghani
> Assignee: Claus Ibsen
> Priority: Minor
>
> Removing an entry (file name) programatically from a file idempotent repository has only effect on the cache and does not get persisted on the file repository.
> There are some situations in which one may need to rerun a file through a workflow and it makes neccessary to remove the file from the idempotent repository. A specific problem arises when upon a server restart, the file is not picked up by the workflow because the remove was not persisted/spooled on the disk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.