java.lang.ClassNotFoundException: org.springframework.web.context.ContextLoaderListener

Question

I included:

all Spring libs,
Apache Tomcat 7.0 library

in Build Path

but it still gives errors:

SEVERE: Error configuring application listener of class org.springframework.web.context.ContextLoaderListener
java.lang.ClassNotFoundException: org.springframework.web.context.ContextLoaderListener
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1676)
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1521)
    at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:415)
    at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:397)
    at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:118)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4660)
    at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5226)
    at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5221)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
Jun 2, 2011 11:07:38 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Error configuring application listener of class org.springframework.web.context.request.RequestContextListener
java.lang.ClassNotFoundException: org.springframework.web.context.request.RequestContextListener
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1676)
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1521)
    at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:415)
    at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:397)
    at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:118)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4660)
    at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5226)
    at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5221)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
Jun 2, 2011 11:07:38 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Error configuring application listener of class com.sun.faces.config.ConfigureListener
java.lang.ClassNotFoundException: com.sun.faces.config.ConfigureListener
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1676)
    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1521)
    at org.apache.catalina.core.DefaultInstanceManager.loadClass(DefaultInstanceManager.java:415)
    at org.apache.catalina.core.DefaultInstanceManager.loadClassMaybePrivileged(DefaultInstanceManager.java:397)
    at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:118)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4660)
    at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5226)
    at org.apache.catalina.core.StandardContext$1.call(StandardContext.java:5221)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)

In "org.sprintframework.web-3.1.0.M1.jar", I can see "org.springframework.web.context.ContextLoaderListener".

Someone on Google says that spring.jar should be included but I don't see any spring.jar in 3.x distribution.

Eclipse 3.6.2 Tomcat 7

Edit: Someone says "Automatically update dependencies" should be checked in Project Properties but I don't see anything like that in project properties. ClassNotFoundException:org.springframework.web.con text.ContextLoaderListener

close the project , create new workplace, make assure about the dependencies in POM. i had to face this problem but was fixed after correction in dependencies — MLS, Jun 2 '11 at 6:59
Can you post the contents of your .war /lib folder please. Or at least everything that is .*spring.*\.jar. — Simeon, Jun 2 '11 at 7:45

Robert J. Walker · Accepted Answer · 2013-12-20 16:11:09Z

up vote 364 down vote accepted

I had a similar problem when running a spring web application in an Eclipse managed tomcat. I solved this problem by adding maven dependencies in the project's web deployment assembly.

Open the project's properties (e.g., right-click on the project's name in the project explorer and select "Properties").
Select "Deployment Assembly".
Click the "Add..." button on the right margin.
Select "Java Build Path Entries" from the menu of Directive Type and click "Next".
Select "Maven Dependencies" from the Java Build Path Entries menu and click "Finish".

You should see "Maven Dependencies" added to the Web Deployment Assembly definition.

edited Dec 20 '13 at 16:11

Robert J. Walker
4,05232453

answered Nov 14 '11 at 21:19

Marcelo
3,672162

4

That is the way you should do it, the correct way in eclipse. – pap Apr 16 '12 at 10:30

11

I was having the same problem. But I cannot see 'Deployment Assembly' at 'Properties' (in a module of my multimodule maven project). – gt_ebuddy Jun 1 '12 at 2:45

3

totally helped, Thanks – chetan Sep 14 '12 at 8:24

2

This was an enormous help. Thanks so much! – mchandler Nov 8 '12 at 18:11

8

This is correct, although highly annoying. Perhaps something m2e plugin should take care of, in my opinion. – RickB May 4 '13 at 0:24

| show 17 more comments

gouki · Answer 2 · 2011-06-02 06:06:15Z

up vote 4 down vote

If you're using maven, perhaps the project aint built yet. First do a 'mvn clean package' then try redeploying again.

answered Jun 2 '11 at 6:06

gouki
2,4891816

Eclipse 3.6.2 + Tomcat 7 – Emerald214 Jun 2 '11 at 6:08

add a comment |

Mashrur · Answer 3 · 2012-04-16 07:04:41Z

up vote 19 down vote

You could try "Clean Tomcat Work Directory" or simply "Clean..". This supposed to discard all published state and republish from scratch.

edited Apr 16 '12 at 7:04

answered Apr 16 '12 at 6:21

Mashrur
23539

Thx for this solution! The accepted answer above didn't solve this issue for me, but yours did. – GreenTurtle Oct 9 '12 at 14:47

This solved my problem too. Thanks! – jlunavtgrad Sep 17 '13 at 17:14

My problem was also solved. Thanks. – Amar Feb 25 at 7:47

add a comment |

italo · Answer 4 · 2013-11-21 16:29:00Z

up vote 53 down vote

Same thing happens to me from time to time when using Eclipse WDT. Its specialy frustrating when this happens to a unmodified and previously working project. This is what I do to fix it in this last scenario:

Stop Tomcat (if it's running)
Open the "Servers" view: Window > Show view > Other > Server > Servers
Right Click on Tomcat Server > Clean Tomcat Work Directory.
Right Click on Tomcat Server > Clean
Restart the server

This usually fixes the issue you mention.

edited Nov 21 '13 at 16:29

italo
3,86811937

answered Sep 5 '12 at 21:41

Chepech
2,14422149

2

There is a bug report for that specific situation (bugs.eclipse.org/bugs/show_bug.cgi?id=365748). Eclipse developers are in need of more informations about it and ways to reproduce the problem. – Chucky Sep 19 '12 at 10:01

good this is the flexible solution for all, this answer must be marked as answer. Good work Chepech – Java Questions Apr 11 '13 at 13:39

3

This is really a simplest solution for this problem. Thanks Chepech! – Badal May 1 '13 at 5:41

Very good. It solved for me. – Alex Aug 19 '13 at 21:18

1

This did not help for me using eclipse 4.4. I had to use Susie's method remove/add deployment to tomcat. I was monitoring the tomcat deployment folder when performing the cleanings. Don't know why cleaning does not clean the the deployment folder. – Blessed Geek Sep 19 '14 at 11:06

| show 1 more comment

abhi · Answer 5 · 2012-10-07 18:47:08Z

I was facing the same issue for a eclipse project configured for Tomcat 7 runtime

Right click on project and go to project properties. Click on Deployment Assembly. I could notice that my spring library jars which I created during compile time with a user library was missing. Just add the jars and you should see no errors in console during tomcat start up

Aditya Gaikwad · Answer 6 · 2012-12-12 11:12:22Z

up vote 5 down vote

This is surely Eclipse related issue. The thing which worked for me is creating a new server in eclipse server tab. Then run your application in this new server, it should work.

answered Dec 12 '12 at 11:12

Aditya Gaikwad
5111

1

@Marcelo worked for me before, but today, I needed this fix. Thanks. – Marvo Jul 25 '13 at 19:42

add a comment |

Volker Demel · Answer 7 · 2013-01-25 10:50:45Z

I tried the

project clean mvn
clean
clean tomcat work directory Automatically
update dependencies

The only thing that worked at least temporarily was to add Maven Dependencies to Web Deployment Assembly definition

But this does not work for ever! After a couple of days it stops working. My solution was to remove Maven Dependencies, apply change and add Maven Dependencies again.

I'm using - eclipse Juno - embedded maven - tomcat 7

kiwifrog · Answer 8 · 2013-07-27 01:31:55Z

Using the "Update project configuartion" messed up the build path of the project.

Fix: Open the "configure build path..." menu (right click on the project) and fix the Included/Excluded options for each source folder. That worked for me.

Prayag Upd · Answer 9 · 2013-09-05 05:38:44Z

For gradle users, It works with following steps

1) Stop and Delete tomcat server from Servers Tab in eclipse

eclipse tomcat tab

2) clean webapp and work directory from tomcat installation , (Reference, How-To: Clear out Tomcat’s cache and fix outdated JSP problems)

$ rm -r /usr/local/AT7028/work/*
$ rm -r /usr/local/AT7028/webapps/WAR_NAME

3) clean and eclipsify project using build tool

$ ./gradlew clean eclipse //fire respective command for mvn users, $ mvn clean package

4) configure a new Tomcat server in eclipse, and run the project again.

Ali.Mojtehedy · Answer 10 · 2013-09-25 17:31:07Z

up vote 0 down vote

In many case It is java facet problem ,jdk or jre or jsp version is difference than maven project face.

answered Sep 25 '13 at 17:31

Ali.Mojtehedy
542311

add a comment |

Neel · Answer 11 · 2013-12-08 16:37:02Z

i too faced the same problem.... and resolved by following the below steps:

RC(right click on web project) --> properties --> Deployment Assembly --> Add --> Java Build Path Entries --> Next --> select jar files which are missing --> next --> finish

Application is running successfully...

Benedikt Köppel · Answer 12 · 2014-09-01 20:14:02Z

You have to use at least version 3.2.8.RELEASE of spring-core.

For Maven, set in your pom.xml:

<dependency>
    <groupId>org.springframework</groupId>
    <artifactId>spring-core</artifactId>
    <version>3.2.8.RELEASE</version>
</dependency>

Source: http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/cglib/core/SpringNamingPolicy.html, since 3.2.8.

Susie · Answer 13 · 2014-09-02 20:51:54Z

If everything mentioned above does not work try the following. It worked for me.

Remove your project from the server > Restart server > Add your project to server > Restart server.

Detailed Instruction:

1. Right click on server > Add and Remove
2. Select your project > Remove > Finish
3. Restart your server
4. Right click on server > Add and Remove
5. Select your project > Add > Finish
6. Restart your server again.

Christian · Answer 14 · 2014-10-22 13:55:25Z

up vote 0 down vote

The actual solution for me was to install the "m2e-wtp - Maven integration for WTP". The solution of Marcelo is not neccessary in that case.

answered Oct 22 '14 at 13:55

Christian
1,802625

add a comment |

Radhakrishnan S · Answer 15 · 2014-12-19 05:57:28Z

Solution for Eclipse Lunca:

Right Click on maven web project
Click 'Properties'menu
Select 'Deployment Assembly' in left side of the popped window
Click 'Add...' Button in right side of the popped up window
Now appear one more popup window(New Assembly Directivies)
Click 'Java Build path entries'
Click 'Next' Button
Click 'Finish' Button, now atomatically close New Assemby Directivies popup window
Now click 'Apply' Button and Ok Button
Run your webapplication

Geo Thomas · Answer 16 · 2015-01-27 05:18:20Z

I have the same issue , and I have resolved it using the steps mentioned above.but no when I have this issue again and i try the following,

RC(right click on web project) --> properties --> Deployment Assembly --> Add --> Java Build Path Entries --> Next -->

after clicking on next its only a blank window with the options Next and Fnish disabled.What can I do now?

asked	3 years ago
viewed	178984 times
active	1 month ago

current community

your communities

more stack exchange communities

java.lang.ClassNotFoundException: org.springframework.web.context.ContextLoaderListener

16 Answers 16

Your Answer

Not the answer you're looking for? Browse other questions tagged spring tomcat7 classnotfoundexception or ask your own question.

Linked

Hot Network Questions

current community

your communities

more stack exchange communities

java.lang.ClassNotFoundException: org.springframework.web.context.ContextLoaderListener

16 Answers 16

Your Answer

Sign up or log in

Post as a guest

Not the answer you're looking for? Browse other questions tagged spring tomcat7 classnotfoundexception or ask your own question.

Linked

Related

Hot Network Questions