log4j :ERROR LogMananger.repositorySelector was null likely due to error
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 Looking into Tomcat/logs/stdout_20100226.log I see: The following critical error occurred: Critical error during OpenCms initialization: Unable to initialize the user driv er. Giving up, unable to start OpenCms. log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository. Starting OpenCms, version 7.5.0 in web application ROOT Copyright (c) 2009 Alkacon Software GmbH OpenCms comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions. Please see the GNU Lesser General Public Licence for further details. I would be glad if I could get some help on m problem getting solved here. Thanks. -- Christoph - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error
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 Looking into Tomcat/logs/stdout_20100226.log I see: The following critical error occurred: Critical error during OpenCms initialization: Unable to initialize the user driv er. Giving up, unable to start OpenCms. log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository. Starting OpenCms, version 7.5.0 in web application ROOT Copyright (c) 2009 Alkacon Software GmbH OpenCms comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions. Please see the GNU Lesser General Public Licence for further details. I would be glad if I could get some help on m problem getting solved here. Thanks. -- Christoph - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error
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
Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error
On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error
Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES Mark Thanks. Great answer! Will try that. Probably will have to try it on 6.0.24 now since I moved to that meanwhile. :) -- Christoph - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error
Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES Mark Excuse me, just one question. Where does this org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES go? catalina.properties? Or is it passed on the commandline? (-D) -- Christoph - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error
On 26/02/2010 11:16, Christoph Kukulies wrote: Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES Mark Excuse me, just one question. Where does this org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES go? catalina.properties? Or is it passed on the commandline? (-D) I normally set in on the command line using the setenv.sh|bat file with CATALINA_OPTS=-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false I think you can also set it in catalina.properties but I'd need to check that to be sure. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error
Mark Thomas schrieb: On 26/02/2010 11:16, Christoph Kukulies wrote: Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES Mark Excuse me, just one question. Where does this org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES go? catalina.properties? Or is it passed on the commandline? (-D) I normally set in on the command line using the setenv.sh|bat file with CATALINA_OPTS=-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false I think you can also set it in catalina.properties but I'd need to check that to be sure. Mark Since passing start parameters under Windows (service manager) is weird somehow I decided to put it in catalina.properties and will see how it works out. -- Christoph - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error
Mark Thomas schrieb: On 26/02/2010 11:16, Christoph Kukulies wrote: Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES Mark Excuse me, just one question. Where does this org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES go? catalina.properties? Or is it passed on the commandline? (-D) I normally set in on the command line using the setenv.sh|bat file with CATALINA_OPTS=-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false I think you can also set it in catalina.properties but I'd need to check that to be sure. Mark Is there a way to interrogate the running tomcat (catalina) process about it's set parameters? I.e., I would like to control whether the setting in the catalina.properties file was fruitful :) -- Christoph - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error
Christoph Kukulies wrote: Mark Thomas schrieb: On 26/02/2010 11:16, Christoph Kukulies wrote: Mark Thomas schrieb: On 26/02/2010 09:47, Christoph Kukulies wrote: I would be glad if I could get some help on m problem getting solved here. http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES Mark Excuse me, just one question. Where does this org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES go? catalina.properties? Or is it passed on the commandline? (-D) I normally set in on the command line using the setenv.sh|bat file with CATALINA_OPTS=-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false I think you can also set it in catalina.properties but I'd need to check that to be sure. Mark Is there a way to interrogate the running tomcat (catalina) process about it's set parameters? I.e., I would like to control whether the setting in the catalina.properties file was fruitful :) Have a look at : http://code.google.com/p/jmxsh/ (It's a generic tool, but quite practical for that kind of thing and more.) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: log4j :ERROR LogMananger.repositorySelector was null likely due to error
From: Christoph Kukulies [mailto:k...@kukulies.org] Subject: Re: log4j :ERROR LogMananger.repositorySelector was null likely due to error Since passing start parameters under Windows (service manager) is weird Use the Java tab of the tomcat6w.exe program to set startup parameters for the service. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
