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 = new ActiveMQConnectionFactory();
connFactory.setBrokerURL(brokerURL);
connFactory.setPrefetchPolicy(prefetchPolicy);
PooledConnectionFactory pcf = new PooledConnectionFactory(connFactory);
pcf.setMaxConnections(50);
JmsTransactionManager jmsTransactionManager = new JmsTransactionManager();
jmsTransactionManager.setConnectionFactory(pcf);
JmsComponent component = ActiveMQComponent.jmsComponentTransacted(pcf,
jmsTransactionManager);
component.getConfiguration().setConcurrentConsumers(50);
this.getContext().addComponent("activemq", component);
...
But, I'm still see the same result. It appears to be throttling down my
HTTP endpoint (maybe including it in the transaction scope??) as I'm only
able to receive ~10 msg/second now (vs. ~250 w/o a transacted route) into my
inbound queue. They are being processed from the queue as fast as they are
coming in...just coming in too slow.
Any other thoughts on this?
thanks again...
-----
Ben - Senior Consultant
--
View this message in context:
http://old.nabble.com/performance-issues-with-JMS-transacted-route...-tp26579725p26618905.html
Sent from the Camel - Users mailing list archive at Nabble.com.
