Pid schrieb:
On 26/02/2010 09:47, Christoph Kukulies wrote:
I'm turning to this mailing list now after I posted my problem to the
Opencms mailing list at opencms.org. And someone from that list gave me
a hint that my problem could possibly have something to do with the
folling citation:

http://mail-archives.apache.org/mod_mbox//logging-log4j-user/200804.mbox/%3c6d42962c-5db1-4acb-bb3a-d9d0d91e9...@apache.org%3e


This is the text I posted to the opencms list and I'm just repeating it
here:


Christoph P. Kukulies schrieb:
> We stop and start Tomcat6.0.10 and Apache2.2 every midnight during the
 > backup of our intranet machine.
 >
 > Since a couple of days the first access in the morning, when the
 > secretary wants to log into opencms, produces the error below:
 >
 >
 > HTTP Status 500 -
 >
 > type Exception report
 >
 > message
 >
> description The server encountered an internal error () that prevented
 > it from fulfilling this request.
 >
 > exception
 >
 > org.opencms.main.CmsInitException: Critical error during OpenCms
 > initialization: Unable to initialize the user driver.
 > org.opencms.main.OpenCmsCore.getInstance(OpenCmsCore.java:290)
 > org.opencms.main.OpenCmsServlet.doGet(OpenCmsServlet.java:127)
 > javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
 > javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 >
> note The full stack trace of the root cause is available in the Apache
 > Tomcat/6.0.10 logs.
 > Apache Tomcat/6.0.10

What happens if you use the latest Tomcat version (rather than one released in Feb 2007)?


p

Will possibly try that. But updating log4j would be less painful if that would solve the problem. Curing problems simply by updating to a newer version could bring other unexpected problems.

--
Christoph


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to