tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Cavanagh <>
Subject Tomcat 7.0.16 won't execute my JSP pages
Date Sat, 03 Sep 2011 20:01:54 GMT
Hello Tomcat users.

I have been a happy Tomcat user since Tomcat 4.x, this will be my first 
post in a long time.

We updated from Tomcat 6.x to Tomcat 7.0.4 a few months ago.  This 
worked just fine.
When I updated to Tomcat 7.0.20 last week, I discovered that our JSP 
pages aren't being executed , rather the server sends back our JSP code 
to the user.  That is not really the desired effect.
After some testing, I discovered that this problem was first introduced 
with Tomcat 7.0.16.  Everything works fine in Tomcat 7.0.14.  There is 
no error being logged by Tomcat.

Our Application is programmed, built and compiled in Netbeans.  It is 
distributed via a WAR file.
The only "special" parts of our web.xml relating to JSP, are that we 
execute jnlp files using the JSP engine (we have dynamic java web start 

There is no error message.
I can see the hits in the localhost_access_log

In the root directory, the index.jsp is executing correctly!

Actually I managed to solve the problem by adding a servlet mapping for jsp.

/Interestingly this problem doesn't occur, when both of these sevlet 
mappings are deleted.
It seems that Tomcat up to 7.0.16 always had a default mapping for *.jsp 
and that from Tomcat 7.0.16 this default mapping only exists, if there 
are no other jsp mappings.
In my case I need both mappings, to ensure that both *.jsp and *.jnlp 
files are executed as jsp.
I haven't tried to find the code that changed, it doesn't really bother 
me having one more mapping in my web.xml#

So maybe this will help some other Tomcat user.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message