camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From damianharvey <>
Subject RE: How to improve Camel MQ performance
Date Sun, 09 Jan 2011 22:17:28 GMT

My Spring JMS configuration (note that I have commented out the transaction handling to improve

      <!-- Beans to create the MQ endpoint using JMS -->

      <bean class="org.springframework.beans.factory.config.MethodInvokingFactoryBean"
p:staticMethod="" />

      <bean id="mqConnectionFactory" class="">
            <property name="hostName" value="${}" />
            <property name="port" value="${mq.port}" />
            <property name="queueManager" value="${mq.queueManager}" />
            <property name="transportType" value="1" />
            <property name="channel" value="SYSTEM.DEF.SVRCONN" />

      <bean id="jmsUserCredentialsFactoryAdapter" class="org.springframework.jms.connection.UserCredentialsConnectionFactoryAdapter">
            <property name="targetConnectionFactory" ref="mqConnectionFactory" />
            <property name="username" value="${jms.username}" />
            <property name="password" value="${jms.password}" />

      <!-- bean id="jtm" class="org.springframework.jms.connection.JmsTransactionManager102">
<constructor-arg index="0" ref="jmsUserCredentialsFactoryAdapter" /> <constructor-arg
            index="1" value="false" /> </bean -->

      <bean id="jc" class="org.apache.camel.component.jms.JmsConfiguration">
            <constructor-arg index="0" ref="jmsUserCredentialsFactoryAdapter" />

      <bean id="mq" class="org.apache.camel.component.jms.JmsComponent">
            <property name="configuration" ref="jc" />
            <property name="acknowledgementModeName" value="AUTO_ACKNOWLEDGE" />
            <property name="transacted" value="false" />
            <!-- property name="transactionManager" ref="jtm" / -->

      <bean id="auditRoute" class="com.aon.camel.routes.impl.AuditRouteBuilder">
            <property name="jmsComponent" ref="mq" />

      <bean id="jmsRoute" class="com.aon.camel.routes.impl.JmsRouterRouteBuilder">
            <property name="jmsComponent" ref="mq" />
            <property name="requestQueue" value="${jms.requestQueue}" />
            <property name="requestQueueOps" value="${jms.requestQueueOps}" />
            <property name="replyQueue" value="${jms.replyQueue}" />

Damian Harvey | Aon Australia/Pacific

Level 31, 201 Kent Street Sydney NSW 2000
t: +61292537000 | f: +61292537952

Please consider the environment before printing this email.
From: Christian Schneider [via Camel] []
Sent: Monday, 10 January 2011 9:14 AM
To: Damian Harvey
Subject: Re: How to improve Camel MQ performance

Can you post your camel jms and configuration?


Am 09.01.2011 22:43, schrieb damianharvey:

> Does anyone have any tips on how to configure Camel to be more performant on
> WebSphere MQ? I haven't seen any settings to allow MQ to use connection
> pooling and I'm finding that it isn't performing well under load - I suspect
> due to the overhead of opening and closing connections (it's about twice as
> slow as the same service over HTTP). I have set the JMS consumer to have 30
> concurrent consumers and this helped a little.
> I have tried adding the following line to the Spring configuration to no
> avail:
> <bean
> class="org.springframework.beans.factory.config.MethodInvokingFactoryBean"
> p:staticMethod="" />
> Is there anything else that I can do? Is anyone using MQ with Camel in a
> high performance environment?
> Thanks,
> Damian.


View message @
To unsubscribe from How to improve Camel MQ performance, click here<>.


This communication (and any attachments) is directed in confidence to the addressee(s) listed
above, and may not otherwise be distributed, copied or used. The contents of this communication
may also be subject to privilege, and all rights to that privilege are expressly claimed and
not waived. If you have received this communication in error, please notify us by reply e-mail
or by telephone and delete this communication (and any attachments) without making a copy.

Before opening or using attachments, you should check them for viruses and defects. We do
not accept liability in connection with computer virus, data corruption, delay, interruption,
unauthorised access or unauthorised amendment.

View this message in context:
Sent from the Camel - Users mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message