-
1. Re: error running jboss
adrian.brock Sep 24, 2002 7:13 AM (in response to jzeil)com.sun.enterprise.util.Utility.getPropertiesFromFile
Looks like you got some jars from the J2ee RI in the
classpath. Check jre/lib/ext if it is not obvious.
Regards,
Adrian -
2. Re: error running jboss
roger01 Sep 24, 2002 8:44 PM (in response to jzeil)I have received a similar set of warnings as follows:
09:51:59,932 WARN [MainDeployer] The manifest entry in file:/etc/jboss-3.0.2/server/default/lib/castor.jar
references URL file:/etc/jboss-3.0.2/server/default/lib/xerces.jar, which could not be opened, entry ignored
09:51:59,932 WARN [MainDeployer] The manifest entry in file:/etc/jboss-3.0.2/server/default/lib/castor.jar
references URL file:/etc/jboss-3.0.2/server/default/lib/jdbc-se2.0.jar, which could not be opened, entry ignored
09:51:59,933 WARN [MainDeployer] The manifest entry in file:/etc/jboss-3.0.2/server/default/lib/castor.jar
references URL file:/etc/jboss-3.0.2/server/default/lib/jndi.jar, which could not be opened, entry ignored
09:51:59,933 WARN [MainDeployer] The manifest entry in file:/etc/jboss-3.0.2/server/default/lib/castor.jar
references URL file:/etc/jboss-3.0.2/server/default/lib/jta1.0.1.jar which could not be opened, entry ignored
09:52:05,282 WARN [MainDeployer] The manifest entry in file:/etc/jboss-3.0.2/catalina/server/lib/commons-logging.jar
references URL file:/etc/jboss-3.0.2/catalina/server/lib/log4j.jar which could not be opened, entry ignored
09:52:05,286 WARN [MainDeployer] The manifest entry in file:/etc/jboss-3.0.2/catalina/server/lib/commons-logging.jar
references URL file:/etc/jboss-3.0.2/catalina/server/lib/log4j-core.jar which could not be opened, entry ignored
09:52:05,287 WARN [MainDeployer] The manifest entry in file:/etc/jboss-3.0.2/catalina/server/lib/tomcat-util.jar
references URL file:/etc/jboss-3.0.2/catalina/server/lib/log4j.jar which could not be opened, entry ignored
09:52:05,287 WARN [MainDeployer] The manifest entry in file:/etc/jboss-3.0.2/catalina/server/lib/tomcat-util.jar
references URL file:/etc/jboss-3.0.2/catalina/server/lib/log4j-core.jar which could not be opened, entry ignored
09:52:05,288 WARN [MainDeployer] The manifest entry in file:/etc/jboss-3.0.2/catalina/server/lib/tomcat-util.jar
references URL file:/etc/jboss-3.0.2/catalina/server/lib/mx4j.jar which could not be opened, entry ignored
The reason for the warnings is that the specified files are not actually present. My question is firstly should these files have come with the download? Secondly do I need these files and if so where should I obtain these files from?
Thanks in anticipation
Roger -
3. Re: error running jboss
adrian.brock Sep 25, 2002 6:02 AM (in response to jzeil)These are third party jars, JBoss provides these
classes using different mechanisms or they are in the
JRE from 1.3+
Regards,
Adrian -
4. Re: error running jboss
roger01 Sep 25, 2002 7:01 AM (in response to jzeil)Does that mean that I can ignore these warnings? Is there any value in removing the class-path entries from the appropriate MANIFEST.MF files and then re-assembling the JAR file, so that these warnings no longer appear?
Regards,
Roger -
5. Re: error running jboss
roger01 Sep 25, 2002 7:11 AM (in response to jzeil)Sorry, I should have mentioned that I am running:
Linux 2.4.9-34,i386 and
Java HotSpot(TM) Server VM 1.4.0-b92,Sun Microsystems Inc.
Regards,
Roger -
6. Re: error running jboss
adrian.brock Sep 25, 2002 8:51 AM (in response to jzeil)Yes you can ignore them.
Change the MANIFEST.MF, if you like.
Regards,
Adrian -