First, undeploy your ear file and start JBoss. It should take about 20-30 seconds to start up after which processor utilization should go down to close to 0%. If that is the case, then there is something in the ear that is causing the problem.
To help locate the problem with the ear, deploy it and when the processor is at 100% utilization take several thread dumps, at about 5 or 10 second intervals (see http://wiki.jboss.org/wiki/Wiki.jsp?page=StackTrace). You should probably redirect the console output to a file so that the dumps do not all scroll off the top of the shell window buffer. The thread dump will show you what threads are active and lead you to the section(s) of the code cuasing the problems. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976661#3976661 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976661 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
