Jboss crashing linux box on shutdown

[roseria]

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

[dlmiles]

Are you sure you want to use JBoss with Java5 (aka 1.5.x). Check out:

About JBoss installation :

http://www.jboss.org/wiki/Wiki.jsp?page=JBossInstallation


About version / naming :

http://java.sun.com/developer/technicalArticles/releases/j2se15/


I notice on the Sun site there is no such thing as J2EE Java5, like there is under J2SE sections.

Maybe I misunderstand but the JBoss install page can be read in one of two ways:

* Written just as 1.5.0beta's were out, means that going beyond 1.4.2 is not recommended yet. (This is the meaning I accepted)

* Written after 1.5.x final release was out, means that using 1.5.x betas is not wise, but if you use 1.5.x final thats ok.

But I would be confused as to why anyone would still be using a Beta when the final thing is released, and further confused why anyone writing that comment wouild not have added "but 1.5.x final is ok" unless of course they did not know that information at the time.

I can report I've had no problems (yet) with operating system interactions with JBoss 4.0.2RC1, Blackdown 1.4.2. Plenty of Java related problems tho, but all part of the struggle up the learning hill :).

[starksm64]

The final jdk5 releases are fine with the latter jboss versions. I have updated the installation page to remove the obsolete jdk5 beta references.

[roseria]

FYI: switched to debian and now all is fine