[
https://issues.apache.org/activemq/browse/SM-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41839#action_41839
]
Guillaume Nodet commented on SM-1292:
-------------------------------------
If you use an incrementing counter in the file name, you don't really need a
locking mechanism, because there will be no conflicts at all. For a
distributed counter, I would think using a database is easier.
> Handle clustering of outbound endpoints using "persisted sequence numbering"
> ----------------------------------------------------------------------------
>
> Key: SM-1292
> URL: https://issues.apache.org/activemq/browse/SM-1292
> Project: ServiceMix
> Issue Type: New Feature
> Components: servicemix-file
> Affects Versions: 3.2.1
> Reporter: Ron Gavlin
>
> The user should be able to configure the output file name as a pattern
> including a "sequence number" (%{<seq_name>}) in the name, such that each
> output file when written out to the target folder has a unique file name that
> embeds the sequence number. The "persisted sequence number" is shared across
> the cluster. See the "Persisted Sequence Number" section of document
> http://wiki.open-esb.java.net/Wiki.jsp?page=FileBindingComponentClusteringSupportImplementation
> for a description of how Sun's OpenESB File Binding Component supports this
> requirement using a control file in the target directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
