[jboss-dev] obtain server connection vs jboss-logging

[Adrian Brock]

On Wed, 2008-10-08 at 14:22 +0300, Aleksandar Kostadinov wrote:
> Hallo,
> 
> Hope I use the right list.

Not really unless this turns out to be a jboss development problem
instead of your mistake.

> *outputs* an exception:
> [server:stop] Shutting down server: profileservice
> [server:stop] java.lang.NoClassDefFoundError: org/apache/log4j/Priority
> [server:stop]   at java.lang.Class.getDeclaredConstructors0(Native Method)
> [server:stop]   at 
> java.lang.Class.privateGetDeclaredConstructors(Class.java:235
> 7)
> [server:stop]   at java.lang.Class.getConstructor0(Class.java:2671)
> [server:stop]   at java.lang.Class.newInstance0(Class.java:321)
> [server:stop]   at java.lang.Class.newInstance(Class.java:303)
> [server:stop]   at 
> org.jboss.logging.Logger.getDelegatePlugin(Logger.java:312)
> [server:stop]   at org.jboss.logging.Logger.<init>(Logger.java:78)
> [server:stop]   at org.jboss.logging.Logger.getLogger(Logger.java:291)
> [server:stop]   at 
> org.jnp.interfaces.NamingContext.<clinit>(NamingContext.java:
> 162)
> [server:stop]   at 
> org.jnp.interfaces.NamingContextFactory.getInitialContext(Nam
> ingContextFactory.java:55)

Your classpath is wrong. You have 
jboss-logging-log4j.jar in the classpath
but not log4j.jar

FIXES:

* Remove jboss-logging-log4j.jar from the classpath
which will then use the "NullLogger"

* add log4j.jar to the classpath