New JBoss User startup woes

[daryllee]

It seems reasonable to me that downloading JBoss-3.2.1 (and maybe even JBoss-3.2.2RC4, both of which I have tried) into a clean directory, with no previous JBoss history on this server, and executing $JBOSS_DIST/bin/run.sh should result in a WARN-free startup. But in my case, and in the case of others (see bluedino's thread on Sep. 22) mutliple .jar files seem to be missing or out of place. The best advice given in that thread was "get a clean distribution and re-install it." I did that using both jboss-3.2.1.zip and ...tgz, and after an hour of trying to track down such files as log4j-core.jar, I'm now ready to plea for help.

Can anyone suggest to me how to get a WARN-free startup? I've tried ignoring the warnings, but a simple hello.war generates exceptions that I think may be traceable to whatever these WARNs are related to.

[juha]

If you're just getting warnings about ignoring manifest entries then you can ignore them. The exceptions you're getting from your hello.war are not related.

-- Juha

[jef.h]

Daryllee,

Check that you've got the environment variable JAVA_HOME setup properly.

... Just my 2cents.

[daryllee]

You are correct that the exceptions in my hello.war are unrelated--they were due to an incorrectly-sequenced web.xml file. It still seems strange to me that it is considered okay to distribute a system that issues warnings such as this, right "out of the box." But who am I to say how an obviously successful product should behave?