Java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory [duplicate]

Java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory [duplicate]

Ask Question

up vote 25 down vote favorite 8	This question already has an answer here: java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory 5 answers Seem to have a problem starting my Java app: Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory at org.apache.catalina.util.LifecycleBase.(LifecycleBase.java:37) Caused by: java.lang.ClassNotFoundException: org.apache.juli.logging.LogFactory at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) ... 1 more Tried the solution here: java.lang.NoClassDefFoundError: org/apache/juli/logging/LogFactory But I see tomcat-juli.jar already. Also I'm using Tomcat 7. What might be wrong? eclipse  tomcat share improve this question edited May 23 at 11:46 Community ♦ 1 1 asked  Oct 31 '11 at 14:55 Mike 844 4 17 37
marked as duplicate by BalusC eclipse Mar 7 '16 at 21:48 This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
	add a comment

7 Answers

active oldest votes

up vote 15 down vote accepted

Your vm does not find the class org/apache/juli/logging/LogFactory check if this class is present in the tomcat-juli.jar that you use (unzip it and search the file), if it's not present download the library from apache web site else if it's present put the tomcat-juli.jar in a path (the lib directory) that Tomcat use to load classes. If your Tomcat does not find it you can copy the jar in the lib directory of the JRE that you are using. share improve this answer answered  Oct 31 '11 at 15:06 Max Zerbini 2,379 13 19

add a comment

up vote 6 down vote	If you are using jsvc to run tomcat as tomcat (run /etc/init.d/tomcat as root), edit /etc/init.d/tomcat and add $CATALINA_HOME/bin/tomcat-juli.jar to CLASSPATH. share improve this answer edited Mar 29 '12 at 22:01 cha0site 7,306 2 23 43 answered  Mar 29 '12 at 21:29 Prasad Bhimaraju 81 1 3
	add a comment

up vote 6 down vote	This happened to me because I was using a Tomcat 5.5 catalina.sh file with a Tomcat 7 installation. Using the catalina.sh that came with the Tomcat 7 install fixed the problem. share improve this answer answered  Mar 14 '13 at 11:19 hertzsprung 3,186 3 25 53
	This is not an answer. This should have been in comments. –  Aditya Singh  Oct 6 '14 at 10:52 4   @AdityaSingh This is an answer. it includes diagnosis of the problem and specification of a resolution. It happens to be succint - which in no way disqualifies it. –  javadba  Mar 8 '16 at 2:02  add a comment

up vote 5 down vote

I ran into this problem when using tomcat-embed-core::7.0.47, from Maven. I'm not sure why they didn't add tomcat-util as a runtime dependency, so I added my own runtime dependency to my own project. <dependency> <groupId>org.apache.tomcat</groupId> <artifactId>tomcat-util</artifactId> <version><!-- version from tomcat-embed-core --></version> <scope>runtime</scope> </dependency> share improve this answer answered  Nov 21 '14 at 17:12 Kyle Krull 783 1 7 17

Helped a lot, using Spring Boot with a Servlet 3.0 compatible version of Tomcat. I had to add this, thanks! (Mine is at scope "provided" currently though). –  electrotype  Nov 3 '16 at 19:42 add a comment

up vote 2 down vote	I had the same problem, What helped me was: Right click on the project. Click 'Properties' Go to 'Java Build Path' And then: 'Libraries' In there, Click: Add External Jars Add: ''Path/To/Tomcat/Bin/tomcat-juli.jar Done . share improve this answer answered  Dec 14 '15 at 8:00 StationaryTraveller 351 4 19
	add a comment

up vote 1 down vote

In our case, the wrong version of the Sysdeo Tomcat plugin for Eclipse 3.5 was being used. The fix: Use tomcatPluginV33 instead of tomcatPluginV321 (extract to C:\eclipse\dropins) Ensure that DevloaderTomcat7.jar was placed in the tomcat lib folder In Window > Preferences > Tomcat, set the Tomcat version to 7.x This problem may have been unique to our environment; but, I'll record it here anyway, for posterity's sake. share improve this answer answered  Mar 27 '12 at 21:33 RMorrisey 5,265 7 35 56

add a comment

up vote 0 down vote	On Ubuntu 14.04 LTS /usr/share# mv /opt/tomcat/apache-tomcat-7.0.56/ tomcat7 fixed the issue for me. There was a symbolic link there to /opt. Inside that opt directory there where ../../java links that would not point to /usr/share/java since the files physically were in /opt share improve this answer answered  Oct 17 '15 at 18:19 Wolfgang Fahl 5,168 3 36 80
	add a comment