Thanks Christian and Raul.
I am not much experienced on camel, so I may use wrong terminology, be aware
of this please.
More details:
I am using camel 2.6.0 at the moment with Sun Java 6 on Linux, and it runs
inside a war deployed on Tomcat 7.
I am configuring it programmatically with RouteBuilder (no xml).
code snippet -a summary-:
-- initialization code--
JndiContext jndiContext = new JndiContext();
CamelContext camelContext = new DefaultCamelContext(jndiContext);
camelContext.addComponent("mycomp0", new MyComp());
camelContext.addComponent("mycomp1", new MyComp());
LoadBalanceDefinition loadBalanceDefinition = new LoadBalanceDefinition();
loadBalanceDefinition = loadBalanceDefinition.roundRobin();
loadBalanceDefinition = loadBalanceDefinition.to("mycomp0:?someparamshere");
loadBalanceDefinition = loadBalanceDefinition.to("mycomp1:?someparamshere");
LoadBalancer loadBalancer = new RoundRobinLoadBalancer();
loadBalancer.addProcessor(loadBalanceDefinition.createProcessor(new
DefaultRouteContext(camelContext)));
from("seda:myqueue?concurrentConsumers=2").loadBalance(loadBalancer);
camelContext.start()
pt = camelContext.createProducerTemplate()
-- msg send code --
for (MyMessage myMessage : messages) {
pt.sendBody("seda:myqueue", myMessage);
}
So as Raul mentioned I figured out there is a concurrentConsumers parameter,
but I just started using it, not sure if it will change something.
Christian, you said sendBody uses InOut pattern, actually I only want InOnly
(only send, no need for return), how can I use it like that ?
Mete
--
View this message in context:
http://camel.465427.n5.nabble.com/seda-queue-performance-tp5068914p5070902.html
Sent from the Camel - Users mailing list archive at Nabble.com.
