Getting java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory exception

Question

i am executing simple Dependency Injection program of spring & getting this exception. I have already included common-logging1.1.1.jar and spring.jar file. Could you please help to out?

Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
    at org.springframework.context.support.AbstractApplicationContext.<init>(AbstractApplicationContext.java:119)
    at org.springframework.context.support.AbstractXmlApplicationContext.<init>(AbstractXmlApplicationContext.java:55)
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:77)
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:65)
    at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:56)
    at com.client.StoryReader.main(StoryReader.java:15)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
    at java.net.URLClassLoader$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    ... 6 more

First, double check that your classpath is indeed correct. Second, try opening the jar and check that it actually contains the org.apache.commons.logging.LogFactory class. Finally, try debugging by setting a breakpoint in the class loader. — Kolibri, Oct 11 '09 at 22:06
All the answers below suggesting ```commons-logging``` is a step backwards. Use ```jcl-over-slf4j``` instead. — opyate, Feb 25 '15 at 16:05
In Android add testCompile 'commons-logging:commons-logging:1.1.1' to app.gradle — Roger Garzon Nieto, Sep 02 '17 at 12:44

score 122 · Answer 1 · answered Jul 03 '13 at 10:49

122

If you're using maven for managing dependencies, add the following line in your pom.xml:

<dependency>
        <groupId>commons-logging</groupId>
        <artifactId>commons-logging</artifactId>
        <version>1.1.1</version>
</dependency>

answered Jul 03 '13 at 10:49

asuka

1,879
3
17
23

score 120 · Answer 2 · edited Jul 18 '11 at 15:41

120

I have also faced the same issues, to fix, download the jar files from the below url

http://commons.apache.org/logging/download_logging.cgi

and copy to your lib folder, will resolve your issue.

edited Jul 18 '11 at 15:41

J. Steen

14,900
15
57
62

answered Jul 18 '11 at 09:28

Manikandan

1,233
1
8
3

2

this doesn't work for me ,even after adding above mentioned commons jar in classpath – Deen John Sep 08 '16 at 20:22
2

Neither for me. These libs are broken. It's so frustating. – Wesos de Queso Jul 30 '17 at 16:53

score 41 · Answer 3 · answered Apr 23 '13 at 07:37

41

You just download commons-logging-1.1.2.jar and then copy this file in to libs

finally, it works.

answered Apr 23 '13 at 07:37

sonida

4,321
1
36
39

score 20 · Answer 4 · answered Jul 17 '14 at 15:38

20

commons-logging-1.1.1.jar or jcl-over-slf4j-1.7.6.jar al

If you are using maven, use the below code.

<dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>jcl-over-slf4j</artifactId>
    <version>${slf4j.version}</version>
</dependency>

answered Jul 17 '14 at 15:38

Paramesh Korrakuti

1,583
3
21
30

2

Including "jcl-over-slf4j" was the only solution that works for me. I already had the commons-logging in my dependencies. – Italo Borssatto May 05 '17 at 19:00
I'm using spring-boot version 2.0.1.RELEASE with maven. This was the only solution that worked for me too. – Carlos Nantes Sep 19 '18 at 18:24

score 18 · Answer 5 · edited Apr 27 '13 at 11:59

18

I had the same problem, and solved it by just adding the commons-logging.jar to the class path.

edited Apr 27 '13 at 11:59

Jesse

8,035
7
42
56

answered Apr 27 '13 at 11:42

stacky

181
1
4

score 8 · Answer 6 · answered Jun 08 '16 at 08:03

8

Adding commons-logging.jar or commons-logging-1.1.jar will solve this...

answered Jun 08 '16 at 08:03

APal

81
1
2

score 7 · Answer 7 · answered Apr 26 '16 at 15:33

7

Setting the scope to compile did it for me

<dependency>
  <groupId>commons-logging</groupId>
  <artifactId>commons-logging</artifactId>
  <version>1.2</version>
  <scope>compile</scope>
</dependency>

answered Apr 26 '16 at 15:33

Patrick Brielmayer

182
1
10

1

Solved my situation. When running Mockito test cases, I got this error and having this dependency in pom.xml solved. – venugopal Jun 30 '17 at 20:38

Jesper · Answer 8 · 2015-03-16T07:39:04.063

6

I have already included common-logging1.1.1.jar and ...

Are you sure you spelled the name of the JAR file exactly right? I think it should probably be commons-logging-1.1.1.jar (note the extra - in the name). Also check if the directory name is correct.

NoClassDefFoundError always means that a class cannot be found, so most likely your class path is not correct.

edited Mar 16 '15 at 07:39

answered Oct 11 '09 at 20:51

Jesper

186,095
42
296
332

2

`NoClassDefFoundError` can also be caused by other corner cases, like when class initializers fail in obscure circumstances. – skaffman Oct 11 '09 at 21:12
Furthermore, if he gets a NoClassDefFoundError because the class instantiation failed, then he should have gotten a ExceptionInInitializerError exception first (unless of course it was caught silently). – Kolibri Oct 11 '09 at 22:04
And don't forget the "s" `commons-logging-1.1.1.jar` – Glenn Lawrence Mar 16 '15 at 00:21
@GlennLawrence Thanks, fixed the name. – Jesper Mar 16 '15 at 07:39

score 4 · Answer 9 · answered Oct 11 '09 at 20:49

Try doing a complete clean of the target/deployment directory for the app to get rid of any stale library jars. Make a fresh build and check that commons-logging.jar is actually being placed in the correct lib folder. It might not be included when you are building the library for the application.

score 4 · Answer 10 · edited Jun 15 '15 at 05:26

Issue solved by adding commons-logging.jar

Imp files are ,

antlr-runtime-3.0.1

org.springframework.aop-3.1.0.M2

org.springframework.asm-3.1.0.M2

org.springframework.aspects-3.1.0.M2

org.springframework.beans-3.1.0.M2

org.springframework.context.support-3.1.0.M2

org.springframework.context-3.1.0.M2

org.springframework.core-3.1.0.M2

org.springframework.expression-3.1.0.M2

commons-logging-1.1.1

score 3 · Answer 11 · answered Jul 23 '15 at 21:25

Two options (at least):

Add the commons-logging jar to your file by copying it into a local folder.

Note: linking the jar can lead to problems with the server and maybe the reason why it's added to the build path but not solving the server startup problem.

So don't point the jar to an external folder.

OR...

If you really don't want to add it locally because you're sharing the jar between projects, then...

If you're using a tc server instance, then you need to add the jar as an external jar to the server instance run configurations.

go to run as, run configurations..., {your tc server instance}, and then the Class Path tab.

Then add the commons-logging jar.

score 3 · Answer 12 · answered Mar 14 '17 at 20:59

I got the same trouble than you. Finally I checked the version of apache possessing the class. I found that the version 1.0.4 has the class.

Try to use the version 1.0.4 instead of 1.1.X or 1.2.X

My dependencies :

    <dependencies>
        <dependency>
            <groupId>org.jolokia</groupId>
            <artifactId>jolokia-core</artifactId>
            <version>1.3.5</version>
        </dependency>
        <dependency>
            <groupId>org.jolokia</groupId>
            <artifactId>jolokia-client-java</artifactId>
            <version>1.3.5</version>
        </dependency>
        <dependency>
            <groupId>commons-logging</groupId>
            <artifactId>commons-logging</artifactId>
            <version>1.0.4</version>
        </dependency>
    </dependencies>

My Java Code

J4pClient j4pClient = new J4pClient("http://localhost:8080/jolokia");
J4pReadRequest req = new J4pReadRequest("java.lang:type=Memory","HeapMemoryUsage");
req.setPath("used");
J4pReadResponse resp = j4pClient.execute(req);
System.out.println(resp.getValue());

My Result :

130489168

Double check also that your maven dependencies are well imported.

score 1 · Answer 13 · answered Jul 30 '12 at 09:09

1

http://commons.apache.org/logging/download_logging.cgi

use this url to download jar files and include them in your class path, issue will be solved

answered Jul 30 '12 at 09:09

rash

19
1

score 0 · Answer 14 · answered Oct 14 '09 at 08:30

0

Just check whether the commons-logging.jar has been added to your libs and the classpath.. I had the same issue and that was because of this. dhammikas-

answered Oct 14 '09 at 08:30

dhammikas

19

score 0 · Answer 15 · answered Dec 24 '09 at 03:14

0

I generally assign the classpath to a variable and then verify it. I've written a small ruby script which I include in a my startup scripts which validates the classpath before launching java. Validating the classpath before the JVM starts has saved me lots of time troubleshooting these types of problems.

answered Dec 24 '09 at 03:14

brianegge

26,898
12
70
97

2

You should consider using tools like Maven instead. – Neovibrant Sep 17 '12 at 00:21

score 0 · Answer 16 · answered Oct 06 '14 at 20:46

Hey I was following the tutorial on tutorialpoint.com. Add after you complete Step 2 - Install Apache Common Logging API: You must import external jar libraries to the project from the files downloaded at this step. For me the file name was "commons-logging-1.1.1".

score 0 · Answer 17 · edited May 23 '17 at 11:55

If you're running this on Android then note that apparently java.beans package is not complete on Android. To attempt to fix it on Android try the following:

Download android-java-air-bridge.jar (currently the download button is on the bottom of the page or direct link here)
Copy the downloaded jar to your [APPROOT]/app/libs directory (or link the jar in any other way)
Change the import *** statements to that of air-bridge. Eg import javadz.beanutils.BeanUtils instead of import org.apache.commons.beanutils.BeanUtils;
Clean and rebuild the project

source 1, source 2

I apologise as I realise this is not exactly answering the question, though this SO page comes up a lot when searching for android-generated NoClassDefFoundError: Failed resolution of: beanUtils errors.

score 0 · Answer 18 · answered Apr 08 '18 at 13:17

0

I was getting the same error while the jar was present. No solution worked. What worked was deleting the jar from the file system (from .m2 directory) and then cleaning the maven project.

answered Apr 08 '18 at 13:17

Anmol Gupta

2,299
5
23
38

score 0 · Answer 19 · answered Jun 12 '18 at 21:09

0

I have the same problem in eclipse IDE, my solution was: Right click in My project > Properties

Click in Maven and write: jar in the Active Maven Project

Finally, Apply and Close

answered Jun 12 '18 at 21:09

Yuliem Alavez

53
1
5

score 0 · Answer 20 · answered Mar 25 '19 at 08:46

In my case I was testing a Tomcat app in eclipse and got this error. I solved it by checking the .classpath file and corrected this entry:

<classpathentry kind="con" path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER">
    <attributes>
        <attribute name="maven.pomderived" value="true"/>
        <attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/>
    </attributes>
</classpathentry>

The attribute org.eclipse.jst.component.dependency had been missing.

score -1 · Answer 21 · answered Sep 16 '14 at 12:00

-1

Check whether the jars are imported properly. I imported them using build path. But it didn't recognise the jar in WAR/lib folder. Later, I copied the same jar to war/lib folder. It works fine now. You can refresh / clean your project.

answered Sep 16 '14 at 12:00

Sibichakravarthy Gunasekaran

1
2

score -2 · Answer 22 · answered Jul 18 '13 at 07:14

Hello friends if your getting any not class found exception in hibernate code it is the problem of jar files.here mainly two problems
1.I mean to say your working old version of hibernate may be 3.2 bellow.So if u try above 3.6 it will works fine

2.first checkes database connection.if it database working properly their was a mistake in ur program or jar file.

please check these two prioblems if it also not working you tried to IDE . I am using netbeanside 6.9 version.here hibernate working fine.you dont get any error from class not founnd exception..

I hope this one helps more

score -2 · Answer 23 · answered Oct 20 '15 at 07:54

-2

try adding this dependency org.apache.commons commons-exec 1.3

answered Oct 20 '15 at 07:54

user1244663

27
1
2

score -3 · Answer 24 · answered Aug 14 '14 at 19:01

-3

If all else fails, as it had for me, try putting the commons-logging-x.y.z.jar in your Tomcat lib directory. It solved the problem! BTW, I am using Tomcat 6.

answered Aug 14 '14 at 19:01

Bob V.

1

name thing? what are you talking about? – Bob V. Aug 14 '14 at 19:22

score -4 · Answer 25 · answered Jul 28 '14 at 07:38

-4

Solution is to Add common-logging.x.x jar file

answered Jul 28 '14 at 07:38

Sachin

59
3

Getting java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory exception

25 Answers25

Linked

Related