You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomcat.apache.org by Christoph Kukulies <ku...@kukulies.org> on 2010/02/26 10:47:25 UTC

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-D9D0D91E9B0B@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

Re: log4j :ERROR LogMananger.repositorySelector was null likely duetoerror

Posted by Christopher Schultz <ch...@christopherschultz.net>.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck,

On 2/26/2010 3:54 PM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:chris@christopherschultz.net] 
>> Subject: Re: log4j :ERROR LogMananger.repositorySelector was null 
>> likely duetoerror
>> 
>> 4) Use jinfo, a program that comes with the JDK for sure, possibly
>> with the JRE as well.
> 
> It doesn't come with the JRE (only the JDK), and it has severe
> limitations on Windows (the OP's platform).  For example, you may
> only look at specific command-line settings, one at a time, and not
> system properties in general.

That's too bad: on *NIX, I can use it to grab all system properties as
well as show me those that were specified on the command-line, etc. :(

One more reason to run *NIX in production. And development. And pretty
much everywhere.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuNTZkACgkQ9CaO5/Lv0PCoGQCfemspeRXNuXDd7tdQchBMPZhR
HY4AoLAbRZMk24k6AA/cRTwPw5P+gJu6
=S0QL
-----END PGP SIGNATURE-----

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

RE: log4j :ERROR LogMananger.repositorySelector was null likely duetoerror

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.

> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Subject: Re: log4j :ERROR LogMananger.repositorySelector was null
> likely duetoerror
> 
> 4) Use jinfo, a program that comes with the JDK for sure, possibly with
> the JRE as well.

It doesn't come with the JRE (only the JDK), and it has severe limitations on Windows (the OP's platform).  For example, you may only look at specific command-line settings, one at a time, and not system properties in general.

 - 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.

Re: log4j :ERROR LogMananger.repositorySelector was null likely dueto error

Posted by Christopher Schultz <ch...@christopherschultz.net>.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck,

On 2/26/2010 9:13 AM, Caldarale, Charles R wrote:
>> From: Christoph Kukulies [mailto:kuku@kukulies.org]
>> Subject: Re: log4j :ERROR LogMananger.repositorySelector was null
>> likely dueto error
>>
>> Is there a way to interrogate the running tomcat (catalina) process
>> about it's set parameters?
> 
> 1) Use JConsole (tricky with a service).
> 
> 2) Install LambdaProbe and look at its System Information -> System Properties page.
> 
> 3) Write a trivial servlet that includes the following code:

4) Use jinfo, a program that comes with the JDK for sure, possibly with
the JRE as well.

Usage: jinfo <pid>

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuIMs4ACgkQ9CaO5/Lv0PBJfACbB4iQB4lAMWj4db60EOzrRDM7
0lYAoJd4ZZLszlPgN/XsmiizICMsoXuk
=02Jq
-----END PGP SIGNATURE-----

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

RE: log4j :ERROR LogMananger.repositorySelector was null likely dueto error

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.

> From: Christoph Kukulies [mailto:kuku@kukulies.org]
> Subject: Re: log4j :ERROR LogMananger.repositorySelector was null
> likely dueto error
> 
> Is there a way to interrogate the running tomcat (catalina) process
> about it's set parameters?

1) Use JConsole (tricky with a service).

2) Install LambdaProbe and look at its System Information -> System Properties page.

3) Write a trivial servlet that includes the following code:

    Properties props = System.getProperties();
    Object[] keys = props.keySet().toArray();

    Arrays.sort(keys);

    for (int i = 0; i < keys.length; i++) {
      response.getWriter().println(keys[i] + "=" + props.getProperty((String)keys[i]));
    }

 - 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org