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 concurrent load.


On Mon, Nov 30, 2009 at 7:40 PM, boday <bo...@vektrel.com> wrote:
>
> I have the following JMS transacted route...
>
> from("activemq:start?maxConcurrentConsumers=50&transacted=true")
> .process(new ValidateMessage())
> .process(new SaveToDatabase())
> .to("activemq:finishedQueue");
>
> I assumed there would be a bit of overhead with using transactions, but my
> route goes from ~250 message/second to ~50 messages/second when I add the
> "?transacted=true" to it (no other changes).
>
> I've seen similar performance hits when I added xpath (content based
> routing, etc) to my route (so I worked around it).  My processor
> "SaveToDatabase" does connect to a database (spring JDBC stored procedure
> call), but is not transactional itself.
>
> Overall, my goal is to simply make my route guarantee messaging (server
> crashes, restarts, etc) and maintain its high throughput.  Any other ideas?
>
> Has anyone else seen this type of drop in throughput with transacted
> messages?  I'm hoping it has something to do with the Tx manager
> configuration or something.  I'm using the default tx.xml file that shipped
> with Servicemix 3.3.1/Camel 2.0...
>
> note: this is a followup to another thread
> (http://old.nabble.com/guaranteed-message-processing-question...-to26202573.html#a26270332)
>
> thanks...
>
> -----
> Ben - Senior Consultant
>
> --
> View this message in context: 
> http://old.nabble.com/performance-issues-with-JMS-transacted-route...-tp26579725p26579725.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>



-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Reply via email to