JBoss tip of the day
If you want to inspect jBoss Thread CPU's usage you have a shortcut from the jmx-console. Point at the Mbean ServerInfo under the domain jboss.system.
This is a shortcut if you're running your server on localhost:
http://localhost:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=jboss.system%3Atype%3DServerInfo
now invoke the operation listThreadCpuUtilization()
| Thread Name | CPU (milliseconds) |
|---|---|
| http-127.0.0.1-8080-1 | 609 |
| ScannerThread | 500 |
| DestroyJavaVM | 125 |
| DefaultQuartzScheduler_QuartzSchedulerThread | 78 |
| ContainerBackgroundProcessor[StandardEngine[jboss.web]] | 15 |
| DefaultQuartzScheduler_Worker-1 | 15 |
| DefaultQuartzScheduler_Worker-5 | 15 |
| Thread-4 | 15 |
Here you can see which threads are pumping the cpu - have a look, besides the threads dedicated to the web applications (running on port 8080) you are using quite a lof of cpu for the ScannerThread which is responsible of period based scanning for the Deployment of applications.
Sure you need to enable Deployment Scanning ? in production enviroment you had better disabling it: have a look here at this tip:<
