On Thu, Dec 3, 2009 at 1:27 AM, boday wrote:
>
> Claus, I tried the following...
>
> -disabled the message groups
> -setup the Spring JmsTransactionManager as follows...
>
> ...
> ActiveMQPrefetchPolicy prefetchPolicy = new ActiveMQPrefetchPolicy();
> prefetchPolicy.setQueuePrefetch(50); //tried
Claus, I tried the following...
-disabled the message groups
-setup the Spring JmsTransactionManager as follows...
...
ActiveMQPrefetchPolicy prefetchPolicy = new ActiveMQPrefetchPolicy();
prefetchPolicy.setQueuePrefetch(50); //tried 0, 10, 1000, 5000
ActiveMQConnectionFactory connFactory = n
Hi
I wonder that JMSXGroupID does affect performance.
> amq.setAcknowledgementModeName("AUTO_ACKNOWLEDGE");
That one should be TRANSACTED
And there should be a setter for transacted on the AMQ as well.
AMQComponent ... setTransacted(true);
Use Spring JmsTransactionManager
btw Camel in Action,
thanks Claus, that is exactly what I wanted to hear...
here is my setup...any advice would be appreciated...
JDK 1.6, ServiceMix 3.3.1, Camel 2.0 (patched the
/hotdeploy/servicemix-camel.zip)
AMQ 5.2 (persistent, small 1k messages, 250+ msg/second, no XA Tx)
Jenks AMQ pool 2.1, Spring 2.5.6
htt
Hi
Also which version of spring are you using? spring-jms is not really
performing well until late 2.5.x versions.
There is a bit snippet about caching and spring issues at
http://camel.apache.org/jms.html
And if using AMQ it has a ton of tuning parameters.
prefretch buffer need to be adjusted t
Hi
You need to post more details about your JMS and TX setup.
Which TX manager are you using? Do you use XA or not.
And the JMS broker I assume its AMQ but if not what is it?
BTW: The xpath thingy should be faster in 2.1 as we have removed a
hotspot which let it perform much better under concurre
