谷歌应用引擎：错误：NOT_FOUND

Question

The app was running well. But after we deployed the version 4, it's showing this error:

Error: NOT_FOUND

No other message.

You can see it here . While deploying eclipse gives a successful message: Task7 successfully deployed to Google App Engine

All the previous versions still run well. The local version also runs okay. Tried to find similar problems and found a few ( 1 , 2 , 3 ) but none of them have any useful solutions.

I don't know whether the web.xml would help to figure out the solution but I am giving it here. Although I checked and found out the web.xml in the previous version (that runs well) and this one is similar.

<?xml version="1.0" encoding="utf-8" standalone="no"?><web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
    <servlet>
        <servlet-name>controller</servlet-name>
        <servlet-class>ebiz.pbj.task7.controller.Controller</servlet-class>
    </servlet>
    <servlet-mapping>
        <servlet-name>controller</servlet-name>
        <url-pattern>*.do</url-pattern>
    </servlet-mapping>

    <servlet-mapping>
        <servlet-name>controller</servlet-name>
        <url-pattern>    /start                   </url-pattern>
    </servlet-mapping>

    <welcome-file-list>
        <welcome-file>    start   </welcome-file>

    </welcome-file-list>
 <servlet>
  <servlet-name>SystemServiceServlet</servlet-name>
  <servlet-class>com.google.api.server.spi.SystemServiceServlet</servlet-class>
  <init-param>
   <param-name>services</param-name>
   <param-value/>
  </init-param>
 </servlet>
 <servlet-mapping>
  <servlet-name>SystemServiceServlet</servlet-name>
  <url-pattern>/_ah/spi/*</url-pattern>
 </servlet-mapping>
 <filter>
        <filter-name>ObjectifyFilter</filter-name>
        <filter-class>com.googlecode.objectify.ObjectifyFilter</filter-class>
</filter>
<filter-mapping>
        <filter-name>ObjectifyFilter</filter-name>
        <url-pattern>/*</url-pattern>
</filter-mapping>
</web-app>

If you need any other code excerpts please let me know and I'll edit my question.

Really confused about what went wrong suddenly. Any help would be welcomed. Thanks.

Answer 1

I think I should share my findings in case someone else gets into the same problem.

This might not be the only cause of the problem because 404: NOT_FOUND can happen for various reasons but this is one of the reasons and people should be aware of it.

The naming of the jsp files are case sensitive . In the controller, we have codes like this :

if (errors.size() != 0) 
{ return "login.jsp"; }

but our login.jsp was mistakenly named as Login.jsp - so it could not find it.