[
https://issues.apache.org/jira/browse/CAMEL-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viktor Schmidt updated CAMEL-4289:
----------------------------------
Description:
We are polling files from a network directory via camel and store them in a
database. Because of performance issues we use 2 server nodes which reading
from one network directory. So the problem is that we have multiple entries in
our database, but only with multiple server nodes. With one node the number of
entries is correct. Our testcase includes 1000 input xml's which should result
in 1000 database entries. The error quote is approximately 1 percent. We think
it's a concurrent lock issue by camel. We could not find topics in your further
release notes, which can fix our issue.
Kind regards
Viktor Schmidt
was:
We are polling files from a network directory via camel and store them in a
database. Because of performance issues we use 2 server nodes which reading
from one network directory. So the problem is that we have multiple entries in
our database, but only with multiple server nodes. With one node the number of
entries is correct. Our testcase includes 1000 input xml's which should result
in 1000 database entries. The error quote is lesser than 0,1 percent. We think
it's a concurrent lock issue by camel. We could not find topics in your further
release notes, which can fix our issue.
Kind regards
Viktor Schmidt
> Concurrent file polling results to multiple processing
> ------------------------------------------------------
>
> Key: CAMEL-4289
> URL: https://issues.apache.org/jira/browse/CAMEL-4289
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.5.0
> Environment: Windows Server 2003, Apache Tomcat 6, JDK 1.6, NTFS
> Filesystem
> Reporter: Viktor Schmidt
>
> We are polling files from a network directory via camel and store them in a
> database. Because of performance issues we use 2 server nodes which reading
> from one network directory. So the problem is that we have multiple entries
> in our database, but only with multiple server nodes. With one node the
> number of entries is correct. Our testcase includes 1000 input xml's which
> should result in 1000 database entries. The error quote is approximately 1
> percent. We think it's a concurrent lock issue by camel. We could not find
> topics in your further release notes, which can fix our issue.
> Kind regards
> Viktor Schmidt
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
