Hi,

Can anyone suggest any performance improvement techniques for camel-activemq

We have tried connection pooling mentioned in this page 
http://camel.apache.org/activemq.html
<http://camel.apache.org/activemq.html>  

Here is my xml and route configuration

from("netty:tcp://10.44.71.187:7000?textline=true").threads(800,800)
.bean(MainDummyProcessor.class)
.to("activemq:CAMEL_ONE_QUEUE?testConnectionOnStartup=true&replyTo=CAMEL_ONE_QUEUE_REP&replyToType=Exclusive");
                                
from("activemq:CAMEL_ONE_QUEUE?testConnectionOnStartup=true&concurrentConsumers=500&maxConcurrentConsumers=500&asyncConsumer=true")
.to("netty:tcp://10.44.71.67:7004?textline=true");



        <bean id="jmsConnectionFactory"
class="org.apache.activemq.ActiveMQConnectionFactory">
                <property name="brokerURL" value="tcp://10.44.71.85:61616" />
        </bean>
        <bean id="pooledConnectionFactory"
class="org.apache.activemq.pool.PooledConnectionFactory"
                init-method="start" destroy-method="stop">
                <property name="maxConnections" value="100" />
                <property name="connectionFactory" ref="jmsConnectionFactory" />
        </bean>

        <bean id="jmsConfig"
class="org.apache.camel.component.jms.JmsConfiguration">
                <property name="connectionFactory" 
ref="pooledConnectionFactory" />
                <property name="concurrentConsumers" value="100" />
        </bean>

        <bean id="activemq"
class="org.apache.activemq.camel.component.ActiveMQComponent">
                <property name="configuration" ref="jmsConfig" />
        </bean>



In the same route Without using activemq we are getting much high
tps(~2500), whereas with activemq its very less (~200) .

Should we use any extra properties while configuring activemq?

camel version : 2.10.3
activemq : 5.7.0




-----
Regards

kiran Reddy
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-Activemq-performance-suggestions-tp5734508.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to