cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TangYong (JIRA)" <>
Subject [jira] [Created] (DOSGI-151) java.lang.NoClassDefFoundError: org/apache/log4j/Logger
Date Tue, 04 Dec 2012 08:26:58 GMT
TangYong created DOSGI-151:

             Summary: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
                 Key: DOSGI-151
             Project: CXF Distributed OSGi
          Issue Type: Bug
          Components: Discovery
    Affects Versions: 1.4
         Environment: 1 JDK 1.6
2 zookeeper-3.4.5
3 Windows XP Sp2
4 DOSGi 1.4 Trunk SnapShot
            Reporter: TangYong

While using DOSGi Discovery with zookeeper, if not putting/installing log4j bundle, the following
exception will be thrown:

D:\gf\org.apache.felix.main.distribution-4.0.3\felix-framework-4.0.3>java -jar bin\felix.jar
*ERROR* [, id=11, bundle=1]: Unexpected problem updating
Configuration PID=org.apache.cxf.dosgi.discovery.zookeeper, factoryPID=null, bundleLocation=file:/D:/gf/org.apache.felix.main.distribution-4.0.3/felix-framework-4.0.3/bundle/cxf-dosgi-ri-singlebundle-distribution-1.4-SNAPSHOT.jar
java.lang.NoClassDefFoundError: org/apache/log4j/Logger
        at org.apache.zookeeper.ZooKeeper.<clinit>(
        at org.apache.cxf.dosgi.discovery.zookeeper.ZooKeeperDiscovery.createZooKeeper(
        at org.apache.cxf.dosgi.discovery.zookeeper.ZooKeeperDiscovery.updated(
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger not found by cxf-dosgi-ri-singlebundle-distribution
        at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(
        at org.apache.felix.framework.BundleWiringImpl.access$400(
        at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(
        at java.lang.ClassLoader.loadClass(
        ... 6 more
Welcome to Apache Felix Gogo

Although this can be considered as a user error, dosgi-discovery[1] should give us more stating
and let user can install log4j bundle in ahead of time.


This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message