I have installed JBoss on a remote linux blade with two AMD Athlon(tm) MP 2600+ cpus.
JBoss starts fine using jboss_init_redhat.sh start, against the default configuration. When jboss_init_redhat.sh stop is run, the java process takes 99% cpu and is unkillable. Its so bad that the linux shutdown -r cmd locks up and requires a manual reboot (an issue for remote server). Using kill -3 on the jboss_init_redhat.sh stop java process completely locks the blade and requires a manual reset. If instead of running the shutdown script you use the JMX console the server may be shutdown normally. However as the JMX console is not secure I dont want to use it remotely. Has anyone else seen this ? ... everything runs fine under XP. Has anyone any idea why the JMX console works but the stop cmd doesnt ? Anyone have any idea how I can safely shutdown jboss without manual intervention ? Once Versions :- (used yum to get latest linux patches) Linux 2.6.5-1.358custom #1 SMP Thu Mar 31 11:47:22 BST 2005 i686 athlon i386 GNU/Linux java version "1.5.0_02" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-b09) Java HotSpot(TM) Server VM (build 1.5.0_02-b09, mixed mode) jboss-4.0.1sp1 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875157#3875157 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875157 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
