"PeterJ" wrote : The best thing to do is get a Java thread dump. I recommend doing three thread dumps at about 10 or 20 second intervals while the CPU usage is high. Examining the threads to see which ones are busy and what code they are executing should help pinpoint the problem. | | Also, what are your JVM command line options? Specifically the heap settings. Thank you Peter, how to take java thread dump. Where so far as jvm option is concerned,its setting is as follows JAVA_OPTS="-server -Xms128m -Xmx1024m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000" the server has 1 gb RAM. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4132721#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...