See Servlet Spec 2.3, section 9.7.2

Posted by
February 16, 2008
  

validateJarFile (C:\jboss\server\default\.\tmp\deploy\tmp49777abc-exp.war\WEB-INF\lib
\servlet.jar) – jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class

I guess this is the most modest and informative error i have come through. This generally happen when you deploy your war file and start the server. Now lets follow the instructions given in error and read through the section 9.7.2.

The classloader that a container uses to load a servlet in a WAR must allow the
developer to load any resources contained in library JARs within the WAR
following normal J2SE semantics using getResource. It must not allow theWAR to
override J2SE or Java servlet API classes. It is further recommended that the loader
not allow servlets in theWAR access to the web container’s implementation classes.
It is recommended also that the application class loader be implemented so
that classes and resources packaged within the WAR are loaded in preference to
classes and resources residing in container-wide library JARs.

The problem is that you are having some of the jar files which are not supposed to be in your war but in container(tomcat) e.g. servlet.jar. It is very common mistake to keep these jars in WEB-INF/lib folder for compilation and ship it with the war file.

Check whether you have any jar files which are not supposed to be with war file but in container’s lib directory.

Most Commented Posts

error, servlet, tomcat, web

If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.

Comments
Comment by Zhao Yichun on April 8, 2008 @ 3:35 pm

thanks. it do help.

Comment by Aditya on April 11, 2008 @ 11:03 am

Thanks Zhao for your comment.

Comment by Joseph on May 12, 2008 @ 8:59 am

This solves my problem, thanks Aditya.

Comment by Aditya on June 2, 2008 @ 6:09 pm

Thanks joseph for your comment. I wrote it down only because this mistake we generally do while developing web in Java.

Comment by Amir Raza on July 16, 2008 @ 10:07 pm

Hi,

If the problem has occured during building the Maven POM then you just need to set the tag under to “provide”.

tomcat
servlet-api
5.5.23
provided

Comment by ok on September 25, 2008 @ 7:31 am

good site nuladx

Comment by sanjay Katiyar on April 17, 2009 @ 12:48 pm

Helpful.
Thanks.

Comment by Aditya on April 18, 2009 @ 5:43 am

Thanks for your comment man!

Comment by Prathik on July 6, 2009 @ 2:05 pm

Hey when I deployed the java application and run on Tomcat I got the following error. Plz let me know what the error is
Thanks in advance
java.lang.reflect.InvocationTargetException
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:440)
com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:279)
com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)
com.opensymphony.xwork2.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:163)
com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:87)

Comment by Uditha Indika Karunaratne on November 8, 2010 @ 11:05 am

thank… i also had the same problem while developing a web service using Axis 2. this help me a lot to solve the problem. because there were some unwanted jar in Axis’s lib folder which already exists in the lib folder of tomcat. so i removed the unwanted jars from the axis’s lib folders.

Leave a comment

(required)

(required)