We are running out of ideas to try. It is odd that JBoss now stops straight away, as it shouldn't be loading anything to do with LAMS at that point - at this stage it should only be loading JBoss at this stage.
Its like the run.sh script is printing out its debugging statements at the top, and then tries to run JBoss and then stops. You have checked the boot.log, and that is the right place to check for any errors that happen at the very beginning of JBoss starting (then it switches to server.log).
Can you try pasting the command at the end of that screen output onto your command line and running that. Do you get any errors? That is:
/usr/java/jdk1.6.0_02/bin/java -server -Xms128m -Xmx128m -Dprogram.name=run.sh -Djava.endorsed.dirs=/usr/local/jboss-4.0.2/lib/endorsed -classpath /usr/local/jboss-4.0.2/bin/run.jar:/usr/java/jdk1.6.0_02/lib/tools.jar org.jboss.Main
Can you also do a quick check of your jboss directory. You should have the following subdirectories and files:
bin
docs
lib
readme_j2ee.html
client
jar-versions.xml
readme.html
server
Then check that there is a directory
"/server/default/deploy/lams.ear" and that it contains about 91 files or directories.
Fiona
Posted by Fiona Malikoff
