I've just installed JBoss 4.0.3 SP1 as a Windows Service using JavaService as per these instructions: http://wiki.jboss.org/wiki/Wiki.jsp?page=RunJBossAsAServiceOnWindows
I had to modify the command line slightly as "JBossService.exe" doesn't exist in the JavaService distro and I also added settings to increase the JVM's initial and maximum heap size.
When we go to replace an existing web-app with a newer version, the old version is undeployed successfully but the new version never gets deployed and CPU usage goes straight to 25% for the JavaService application. Restarting the service solves the problem (and JBoss responds to the "stop service" command), but obviously this isn't ideal.
Any help would be much appreciated.