Hi,
I am not sure if this is a bug, or if there is a way around it, but either
way, I wrote a small sample to reproduce the problem I am facing in my
application.
Setup
- camel 2.4.0
- running on Windows 32 bits
- Sun jdk 1.6.0_03
input
2 x .csv files where each one contains 4 tokens separate
This piece of code is a very simplified version of my real code. My
application is running on an OSGi container and the different stages in my
processing are isolated in different bundles. So when I need to pass a
message from one stage to another, I need to use a 'vm' endpoint, a.k.a. a
seda qu
Is there a link I can use to download 2.5.0 (links on
http://camel.apache.org/camel-250-release.html do not work), or I need to go
through the code repo?
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-calling-commit-too-early-when-using-split-seda-file-endpoint-tp283089
I've tried smcduff's patch on 2.4.0 and it fixed my problem. Like he has
mentioned on https://issues.apache.org/activemq/browse/CAMEL-3121, we had to
modify his original patch slightly to make it work at shutdown time. I'll
still give 2.5.0 a try when I get access to it.
--
View this message in
Claus,
can you try the following piece of code and check if it works or not? (it
doesn't work on my workstation, using camel 2.5.0)
Code
from("file:e:/test")
.split(body().tokenize(","))
.log("Split line ${body}")
.process(new Processor()
{
public void process(Exchange e)
Claus,
is there a new snapshot of 2.5.0 that I can use to test your fix? The one
on the Maven repo
(https://repository.apache.org/content/repositories/snapshots/org/apache/camel/camel-core/2.5-SNAPSHOT/)
is too old (Aug 10th). All my stuff is on a private network, so I can't
access your SVN d
Sorry for the late reply, but I had the chance to try out your latest version
of 2.5.0 this morning and I can confirm that your fix worked.
Thanks! :)
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-calling-commit-too-early-when-using-split-seda-file-endpoint-tp28308
Hi,
my system is generating a lot of exchanges (many concurrent threads), so
many that creating an exchange becomes a bottleneck. An exchangeId is
created by the UuidGenerator class, which is using
java.security.SecureRandom. SecureRandom then calls its secureRandomSpi:
UuidGenerator.generat
