While analyzing the performance of my app, which runs on JBoss 3.2.5, I noticed
significant cpu usage eaten up by my JMS queue's message history counter. I figured I
could easily disable this by setting the MessageCounterHistoryDayLimit to zero, as
show in the descriptor below. This resulted in a NullPointerException at startup
caused by the jmx config service calling a setter on the underlying queue object
before it was instantiated. Is there another way that I should disable this count
history feature?
<depends
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
0
true
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852081#3852081
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852081
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
