ansaurus

Question

Answer 1

+4 A:

java.lang.NoClassDefFoundError: org/apache/log4j/spi/RepositorySelector

This means that the in the message mentioned class is missing in the classpath during runtime (while it was available during compiletime of the calling class in question, that's the difference with ClassNotFoundException).

As this is used by Log4j itself, it's thus missing in the Log4j JAR file. The RepositorySelector javadoc learns us that it's introduced in Log4j 1.2. This would mean that there's a collision with another and older-versioned Log4j JAR file in the classpath which got precedence in classloading. It's likely somewhere hidden in one of the default classpaths of Weblogic. I don't do Weblogic, but as hinted by others, you can also try to change the classloading order, if it's supported by Weblogic. Consult its documentation.

BalusC 2010-01-20 00:42:41

This has always been a problem with commonly used libraries like log4j or JSF implementation. I don't know about weblogic, in websphere there is an option to set classloader precedence from parent down to childen (container level down to ear to war level classloader) or the other way around..so it will use your deployed log4j.jar instead of container version.

DJ 2010-01-20 00:50:02

I'm sorry but, no, the solution is not that simple ("clean up and replace") as you didn't take into account the specificities of a startup class (deployment, packaging, classloading, etc).

Pascal Thivent 2010-01-20 01:33:48

Point taken, phrase removed.

BalusC 2010-01-21 01:44:20

Answer 2

+1 A:

where myApp.LoggerStartupService is the class implemented from ApplicationLifecycleListener.

Ok, so you implemented a startup class.

I checked the classpath in my scripts and its set properly for all dependencies required for log4j. Appenders & Categories are also there in the log4j.xml.

How did you setup that classpath? How did you package your startup class and where did you put it? Also, where is log4j.jar, which one do you use? Your startup class (and its dependencies) must be added to the server CLASSPATH. Is this what you did? Refer to Add startup and shutdown classes to the classpath in the official documentation for the details on how to do this.

I'd like to get confirmation of these points (but the final answer is that you should use a MANIFEST.MF in the jar of your startup class to reference third party libraries).

Pascal Thivent 2010-01-20 00:51:45

ansaurus

tags:

views:

answers:

Unable to initalize log4j

related questions