Why don't you use JBossProfiler on that? You can keep the profiler off until you get the 100% of CPU, and make it active when you got the high consumption of CPU. The reports you get will tell exactly what's going on inside the JVM.
Actually I've created JBossProfiler (Well... of course I didn't have that name that time) 1 year and 1/2 ago in the same kind of problem. That's when I came developing the profiler. Clebert View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3851429#3851429 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3851429 ------------------------------------------------------- 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
