we turned off a significant amount of db udpating, and we got a 3-4 fold
performance increase, so it looks as though this is the problem. We are now
going to spend the time tuning our database access some more.
Thanks for helping us identify this as the source of our problem.
View the original
you should verify your last hypothesis by simply outcommenting all processing
code within the MDB and check request latency once again. If it is still high,
that it's an indicator for the 'messaging bottelneck'.
Do you use persistent messages ? If so do you have enough connections in your
conne
Sure. Profile the database server iteraction.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3902539#3902539
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3902539
---
The CPU is not running at even close to 100%. To be honest, I can't figure out
exactly where the bottleneck is, I only know that it goes if I turn off the
MDB. We are using hibernate to perform lookups and update status as a message
travels through the system, could this be causing a bottleneck?
The logic of lowering the priority of the MDB escapes me. If slogging data
between tomcat and the client is not the bottleneck, why shouldn't the priority
be given to the MDBs? If your saturating the cpu on the box and this is the
cause of the increased request latency, you certainly do need to
Sorry, forgot to add: Running JBoss 3.2.7 on RedHat AS4, dual HT Xeons, 4gig
ram, talking to an Oracle db
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3902532#3902532
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=repl
