I've read the entire thread and decided to go back to the original post
for a re-read.
Have you considered the possibility that your tomcat (or wtp) install
has suffered some corruption during the HD crash? You might want to try
backing up the current setup, then re-install and add back in your
webapp and other customizations. Test at various places along the way
until it all works or breaks. If a fresh install works and then breaks
after adding something back in, you've found the issue.
As to the location of log4j.properties, the ideal is to place one for
the server in server/classes for tomcat's internal classloader and one
in each webapp's WEB-INF/classes folder for each webapp's logging. If
you place log4j.properties in common/lib, it becomes the log4j config
for all of tomcat -- the server's internal working and your webapps.
I would recommend you don't mess with trying to set classpath for tomcat
unless you absolutely have to.
--David
Pierre Goupil wrote:
Hi all !
I once had a Tomcat 5.5 and an Eclipse 3.2 that where running just
fine and
then... the HDD crashed... I suffered no data lost but since then, I
can't
start Tomcat anymore. The "server" view of Eclipse gives me the following
trace :
********************************
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: com.sun.org.apache.commons.logging.LogConfigurationException:
com.sun.org.apache.commons.logging.LogConfigurationException :
java.lang.NullPointerException (Caused by java.lang.NullPointerException)
(Caused by com.sun.org.apache.commons.logging.LogConfigurationException:
java.lang.NullPointerException (Caused by
java.lang.NullPointerException ))
at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.newInstance(
LogFactoryImpl.java:543)
at com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getInstance(
LogFactoryImpl.java:235)
at
com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getInstance (
LogFactoryImpl.java:209)
at
com.sun.org.apache.commons.logging.LogFactory.getLog(LogFactory.java
:351)
at org.apache.catalina.startup.Bootstrap.<clinit>(Bootstrap.java:73)
Caused by: com.sun.org.apache.commons.logging.LogConfigurationException :
java.lang.NullPointerException (Caused by java.lang.NullPointerException)
at
com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(
LogFactoryImpl.java:397)
at
com.sun.org.apache.commons.logging.impl.LogFactoryImpl.newInstance (
LogFactoryImpl.java:529)
... 4 more
Caused by: java.lang.NullPointerException
at
com.sun.org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(
LogFactoryImpl.java:374)
... 5 more
********************************
I eventually felt into Commons-logging / Log4j neighborhood jam ! The log
system of my servlet (Log4j) doesn't work anymore, but I don't bother
because it doesn't start anyway. But, regarding Tomcat's log system
re-launching, it's an usual concern : lots of people talk about that. But
neither them nor me can find a solution. Of course I've found a lot of
tutorials, but they can't help...
I have re-installed my workstation, indeed.
I've tried to launch Tomcat via another plugin, too. I gave Sysdeo a
try :
Tomcat runs, loads the servlet, but doesn't run it and keeps quiet. No
servlet log, no exception, no result ("resource unavailable").
If someone could help me find a definitive answer to that classical
question... (other than "42", of course ;-).
Thanx a lot and excuse me for my poor English, I'm a little froggie.
Pierre
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
