Bug 53574 - metadata-complete="true" and servlet defined as jsp not working
Summary: metadata-complete="true" and servlet defined as jsp not working
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 7
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 7.0.29
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-20 09:35 UTC by Mirek
Modified: 2012-08-11 19:01 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mirek 2012-07-20 09:35:23 UTC 
We have a servlet defined as 

<servlet>
        <servlet-name>VersionInfoServlet</servlet-name>
        <jsp-file>/WEB-INF/svnrevision.jsp</jsp-file>
</servlet>

and mapped as 

<servlet-mapping>
        <servlet-name>VersionInfoServlet</servlet-name>
        <url-pattern>/svnrevision</url-pattern>
</servlet-mapping>



It worked fine. Then we changed metadata-complete to "true", and from now on we receive 

INFO: Marking servlet VersionInfoServlet as unavailable
lip 20, 2012 11:05:36 AM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Allocate exception for servlet VersionInfoServlet
javax.servlet.ServletException: No servlet class has been specified for servlet VersionInfoServlet
        at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1130)
        at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:857)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:136)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
        at org.apache.coyote.ajp.AjpNioProcessor.process(AjpNioProcessor.java:184)
        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:722)
Comment 1 Amb 2012-08-10 02:10:51 UTC 
Is this a bug in Tomcat or is the descriptor need something different?  

This project also hit by this issue:
http://code.google.com/p/pwm/issues/detail?id=244
Comment 2 Mark Thomas 2012-08-11 18:34:02 UTC 
This looks like a Tomcat bug. I have a test case for trunk that reproduces this and am working on a fix.
Comment 3 Mark Thomas 2012-08-11 19:01:28 UTC 
This has been fixed in trunk and 7.0.x and will be included in 7.0.30 onwards.