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'
I've encountered the similar problem and can't deal with it.
The thing is, the amount of threads is growing unpredictably, and it's hard to figure
out the reason. Maybe, it depends on JMS options (messages aren't killed immediately)?
My JBoss start options are ok.
Can anyone help me?
View the or
Get a stack trace. Figure out where your application or JBoss is looped.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3850998#3850998
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3850998
--
What are your jboss start parameters ?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3850651#3850651
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3850651
---
This S
