wondering anybody got a clue? will appreciate any idea.
it gets stuck as below, and cpu goes 100% on java.exe. I have upgraded java from 1.5 to 1.6 but same issue. on windows xp sp2.
C:\apps\jboss-4.2.1.GA\bin>run =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: C:\apps\jboss-4.2.1.GA JAVA: C:\apps\Java\jdk1.6.0_03\bin\java JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.r mi.dgc.server.gcInterval=3600000 CLASSPATH: C:\apps\Java\jdk1.6.0_03\lib\tools.jar;C:\apps\jboss-4.2.1.GA\bin\run.jar =============================================================================== 00:10:34,859 INFO [Server] Starting JBoss (MX MicroKernel)... 00:10:34,859 INFO [Server] Release ID: JBoss [Trinity] 4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=2007071316 05) 00:10:34,859 INFO [Server] Home Dir: C:\apps\jboss-4.2.1.GA 00:10:34,859 INFO [Server] Home URL: file:/C:/apps/jboss-4.2.1.GA/ 00:10:34,875 INFO [Server] Patch URL: null 00:10:34,875 INFO [Server] Server Name: default 00:10:34,875 INFO [Server] Server Home Dir: C:\apps\jboss-4.2.1.GA\server\default 00:10:34,875 INFO [Server] Server Home URL: file:/C:/apps/jboss-4.2.1.GA/server/default/ 00:10:34,875 INFO [Server] Server Log Dir: C:\apps\jboss-4.2.1.GA\server\default\log 00:10:34,890 INFO [Server] Server Temp Dir: C:\apps\jboss-4.2.1.GA\server\default\tmp 00:10:34,890 INFO [Server] Root Deployment Filename: jboss-service.xml 00:10:35,312 INFO [ServerInfo] Java version: 1.6.0_03,Sun Microsystems Inc. 00:10:35,312 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0_03-b05,Sun Microsystems Inc. 00:10:35,328 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 00:10:35,687 INFO [Server] Core system initialized 00:10:38,171 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/ 00:10:38,171 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 00:10:38,781 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 00:10:38,781 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 00:10:39,078 INFO [TransactionManagerService] Starting recovery manager
Sounds like JTA is attempting to do a recovery, which was probably caused by bringing the app server down in a non-clear manner (BSOD, for example). I can see where this would be CPU-heavy. You could try taking thread dumps to see what the threads are doing. You should also ask this question in the "JBoss Transactions" forum; if you are confident that your database is correct there are probably some files you could delete to prevent the recovery.
thanks Peter, I do bring down server in unusualy manner (kill it from taks manager). because it throws permGen error every now and then and gets stuck there. perhaps I should move it to windows server machine and see how ti goes. I guess my database is ok, its SQL server 2005 database and I believe db structures etc is all neat.