Databases
StackOverflow2013
Postsdbo
POError after deploying the application in appspot
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POError after deploying the application in appspot
    primarykey
    data
    text
    <p>I get the following error in the browser when trying to access my Java application in appspot. </p> <pre><code>Error: NOT_FOUND </code></pre> <p>However it works fine when I run from Eclipse or ant. I have checked the logs in GAE admin console but couldn't find any error messages.</p> <p>I have also tried by removing all the *.class files before building.</p> <p>The application is deployed using the appcfg script provided in appengine-java-sdk-1.5.3. Is there any specific reason for this behaviour?</p> <p>Here is the debug messages from GAE log console:</p> <pre><code>2011-10-02 22:11:39.306 / 302 14950ms 10348cpu_ms 315api_cpu_ms 0kb Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 115.119.214.18 - - [02/Oct/2011:22:11:39 -0700] "GET / HTTP/1.1" 302 191 - "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1" "xxxxxxxx-test.appspot.com" ms=14950 cpu_ms=10348 api_cpu_ms=315 cpm_usd=0.287514 loading_request=1 throttle_code=1 instance=00c61b117c46324075b13d0c2ce04f5678c813 I 2011-10-02 22:11:26.447 javax.servlet.ServletContext log: Initializing Spring root WebApplicationContext W 2011-10-02 22:11:26.728 [s~xxxxxxxx-test/8.353561328003056299].&lt;stderr&gt;: log4j:WARN No appenders could be found for logger (org.springframework.web.context.ContextLoader). W 2011-10-02 22:11:26.728 [s~xxxxxxxx-test/8.353561328003056299].&lt;stderr&gt;: log4j:WARN Please initialize the log4j system properly. I 2011-10-02 22:11:37.075 javax.servlet.ServletContext log: Initializing Spring FrameworkServlet 'dispatcher' I 2011-10-02 22:11:39.306 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This request may thus take longer and use more CPU than a typical request for your application. </code></pre> <p>web.xml:</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" version="2.5"&gt; &lt;filter&gt; &lt;filter-name&gt;springSecurityFilterChain&lt;/filter-name&gt; &lt;filter-class&gt;org.springframework.web.filter.DelegatingFilterProxy&lt;/filter-class&gt; &lt;/filter&gt; &lt;filter-mapping&gt; &lt;filter-name&gt;springSecurityFilterChain&lt;/filter-name&gt; &lt;url-pattern&gt;/*&lt;/url-pattern&gt; &lt;/filter-mapping&gt; &lt;context-param&gt; &lt;param-name&gt;contextConfigLocation&lt;/param-name&gt; &lt;param-value&gt;/WEB-INF/spring/*.xml&lt;/param-value&gt; &lt;/context-param&gt; &lt;listener&gt; &lt;listener-class&gt;org.springframework.web.context.ContextLoaderListener&lt;/listener-class&gt; &lt;/listener&gt; &lt;servlet&gt; &lt;servlet-name&gt;dispatcher&lt;/servlet-name&gt; &lt;servlet-class&gt;org.springframework.web.servlet.DispatcherServlet&lt;/servlet-class&gt; &lt;init-param&gt; &lt;param-name&gt;contextConfigLocation&lt;/param-name&gt; &lt;param-value&gt;/WEB-INF/spring/servlet-config.xml&lt;/param-value&gt; &lt;/init-param&gt; &lt;load-on-startup&gt;1&lt;/load-on-startup&gt; &lt;/servlet&gt; &lt;servlet-mapping&gt; &lt;servlet-name&gt;dispatcher&lt;/servlet-name&gt; &lt;url-pattern&gt;/ExampleApp/*&lt;/url-pattern&gt; &lt;/servlet-mapping&gt; &lt;welcome-file-list&gt; &lt;welcome-file&gt;index.jsp&lt;/welcome-file&gt; &lt;/welcome-file-list&gt; &lt;/web-app&gt; </code></pre> <p>Contents of index.jsp (welcome-file)</p> <pre><code>&lt;% response.sendRedirect("/ExampleApp/user/login"); %&gt; </code></pre> <p>Here is the build.xml:</p> <pre><code>&lt;project&gt; &lt;property name="sdk.dir" location="../appengine-java-sdk-1.5.3" /&gt; &lt;import file="${sdk.dir}/config/user/ant-macros.xml" /&gt; &lt;path id="project.classpath"&gt; &lt;pathelement path="war/WEB-INF/classes" /&gt; &lt;fileset dir="war/WEB-INF/lib"&gt; &lt;include name="**/*.jar" /&gt; &lt;/fileset&gt; &lt;fileset dir="${sdk.dir}/lib"&gt; &lt;include name="shared/**/*.jar" /&gt; &lt;/fileset&gt; &lt;/path&gt; &lt;!-- &lt;target name="copyjars" description="Copies the App Engine JARs to the WAR."&gt; &lt;copy todir="war/WEB-INF/lib" flatten="true"&gt; &lt;fileset dir="${sdk.dir}/lib/user"&gt; &lt;include name="**/*.jar" /&gt; &lt;/fileset&gt; &lt;/copy&gt; &lt;/target&gt; --&gt; &lt;target name="compile" description="Compiles Java source and copies other source files to the WAR."&gt; &lt;mkdir dir="war/WEB-INF/classes" /&gt; &lt;copy todir="war/WEB-INF/classes"&gt; &lt;fileset dir="src"&gt; &lt;exclude name="**/*.java" /&gt; &lt;/fileset&gt; &lt;/copy&gt; &lt;javac srcdir="src" destdir="war/WEB-INF/classes" classpathref="project.classpath" debug="on" /&gt; &lt;/target&gt; &lt;target name="datanucleusenhance" depends="compile" description="Performs JDO enhancement on compiled data classes."&gt; &lt;enhance_war war="war" /&gt; &lt;/target&gt; &lt;target name="runserver" depends="datanucleusenhance" description="Starts the development server."&gt; &lt;dev_appserver war="war" /&gt; &lt;/target&gt; &lt;target name="update" depends="datanucleusenhance" description="Uploads the application to App Engine."&gt; &lt;appcfg action="update" war="war" /&gt; &lt;/target&gt; &lt;target name="update_indexes" depends="datanucleusenhance" description="Uploads just the datastore index configuration to App Engine."&gt; &lt;appcfg action="update_indexes" war="war" /&gt; &lt;/target&gt; &lt;target name="rollback" depends="datanucleusenhance" description="Rolls back an interrupted application update."&gt; &lt;appcfg action="rollback" war="war" /&gt; &lt;/target&gt; &lt;target name="request_logs" description="Downloads log data from App Engine for the application."&gt; &lt;appcfg action="request_logs" war="war"&gt; &lt;options&gt; &lt;arg value="--num_days=5"/&gt; &lt;/options&gt; &lt;args&gt; &lt;arg value="logs.txt"/&gt; &lt;/args&gt; &lt;/appcfg&gt; &lt;/target&gt; &lt;/project&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USlibregeek
    1. USlibregeek
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI assume you're seeing that in your browser when you try your app's URL. Is that all you're seeing? Is there a stack trace of any sort?
      singulars
      1. POError after deploying the application in appspot
      1. USDave W. Smith
    2. COYes, the **Not found** is the only error message I can see in the browser. I have added the debug messages from GAE log console. The application is running without any problems in Eclipse and ant.
      singulars
      1. POError after deploying the application in appspot
      1. USlibregeek
    3. COI'm pretty sure that error isn't one of AppEngine's. Is it possible that some configuration bit of Spring isn't in your `war` folder?
      singulars
      1. POError after deploying the application in appspot
      1. USDave W. Smith
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload