Tomcat 5 + log4j

Wolfgang Zitzelsberger

unread,

Apr 9, 2004, 3:50:25 PM4/9/04

to

Hi,

hat jemand Tomcat 5 mit einer Webanwendung, die log4j verwendet am
Laufen? Ich bekomme nur noch Fehlermeldungen, sobald das log4j-jar im
lib Verzeichnis der Anwendung oder im lib Verzeichnis von Tomcat liegt.

Grüße,
Wolfgang

erikthewikkinger

unread,

Apr 10, 2004, 3:59:39 AM4/10/04

to

Wolfgang Zitzelsberger wrote:

poste mal ins forum-->http://www.jsp-develop.de
oder gehe dort auf die suche!

hth
erik

Andreas Jaeger

unread,

Apr 11, 2004, 5:53:10 AM4/11/04

to

Wolfgang Zitzelsberger wrote:

> Hi,
>
> hat jemand Tomcat 5 mit einer Webanwendung, die log4j verwendet am
> Laufen?

Ich.

> Ich bekomme nur noch Fehlermeldungen, sobald das log4j-jar im
> lib Verzeichnis der Anwendung oder im lib Verzeichnis von Tomcat liegt.

Welche Fehlermeldungen?

Andreas

Wolfgang Zitzelsberger

unread,

Apr 11, 2004, 7:54:14 AM4/11/04

to

> Welche Fehlermeldungen?
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:306)
at java.lang.Class.newInstance(Class.java:259)
at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:218)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:375)
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: No suitable Log
constructor [Ljava.lang.Class;@158b649 for
org.apache.commons.logging.impl.Log4JLogger
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
at
org.apache.catalina.core.StandardService.<clinit>(StandardService.java:96)
... 8 more
Caused by: org.apache.commons.logging.LogConfigurationException: No
suitable Log constructor [Ljava.lang.Class;@158b649 for
org.apache.commons.logging.impl.Log4JLogger
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:432)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
... 12 more
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1590)
at java.lang.Class.getConstructor0(Class.java:1762)
at java.lang.Class.getConstructor(Class.java:1002)
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:429)
... 13 more

Andreas Jaeger

unread,

Apr 11, 2004, 12:13:35 PM4/11/04

to

> Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:1590)
> at java.lang.Class.getConstructor0(Class.java:1762)
> at java.lang.Class.getConstructor(Class.java:1002)
> at
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:429)

Das sieht mir schwer danach aus, als ob nicht zuviele log4j.jar in
Deinem Tomcat liegen, sondern zu wenige. Jedenfalls sagt die API für
NoClassDefFoundError:

public class NoClassDefFoundError
extends LinkageError

Thrown if the Java Virtual Machine or a ClassLoader instance tries to
load in the definition of a class (as part of a normal method call or as
part of creating a new instance using the new expression) and no
definition of the class could be found.

The searched-for class definition existed when the currently executing
class was compiled, but the definition can no longer be found.

Andreas