I'm using Eclipse to develop and test a new GWT application. Everything appears to work, however when I click the URL to launch it, it leaves the browser in a "loading" status and never actually displays the application. There is no indication of an error in the console.
I've tried accessing the admin url and get the same thing -- just hangs forever with a "loading status" despite the fact that the last line console output reads:
"INFO: The admin console is running at [URL removed so I can post...]"
Full output is below. Any idea what might be wrong or where I could look to figure out how to fix this?
My console output is this:
Dec 19, 2011 4:20:47 PM com.google.apphosting.utils.jetty.JettyLogger info
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Dec 19, 2011 4:20:48 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed C:\Documents and Settings\dhamilton\My Documents\Test1\war\WEB-INF/appengine-web.xml
Dec 19, 2011 4:20:48 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed C:\Documents and Settings\dhamilton\My Documents\Test1\war\WEB-INF/web.xml
Dec 19, 2011 10:20:53 AM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The server is running at http://localhost:8888/
Dec 19, 2011 10:20:53 AM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The admin console is running at http://localhost:8888/_ah/admin
Related
It works well yesterday afternoon, but it does not work now.
I use goapp deploy MY_DIR/app.yaml to deploy, and this is the message of deploy
02:38 PM Host: appengine.google.com
02:38 PM Application: MY_APP; module: MY_MOD; version: MY_VER
02:38 PM Starting update of app: exp-lkl, module: MY_MOD, version: MY_VER
02:38 PM Getting current resource limits.
02:38 PM Scanning files on local disk.
02:38 PM Scanned 500 files.
02:38 PM Scanned 1000 files.
02:38 PM Cloning 1085 application files.
02:38 PM Compilation starting.
02:38 PM Compilation: 1081 files left.
02:38 PM Compilation completed.
02:38 PM Starting deployment.
02:38 PM Checking if deployment succeeded.
02:38 PM Will check again in 1 seconds.
02:38 PM Checking if deployment succeeded.
02:38 PM Will check again in 2 seconds.
02:38 PM Checking if deployment succeeded.
02:38 PM Will check again in 4 seconds.
02:38 PM Checking if deployment succeeded.
02:38 PM Will check again in 8 seconds.
02:38 PM Checking if deployment succeeded.
02:38 PM Will check again in 16 seconds.
02:38 PM Checking if deployment succeeded.
02:39 PM Deployment successful.
02:39 PM Checking if updated app version is serving.
02:39 PM Rolling back the update.
Error 500: --- begin server output ---
Server ErrorA server error has occurred.
--- end server output ---
I tried also:
1/ update sdk to the lastest version
2/ update go version (I tried go1.6 and go1.8)
3/ use appcfg.py
But I get the same error
Someone can help?
Finally I fixed this issue.
It seems that app engine changed the error message for the no buildable code. My project does not build, app engine showed the path of the no buildable code before, but now app engine returns 500 error
Error 500:
--- begin server output ---
<h3>Server Error</h3><p>A server error has occurred.</p>
--- end server output ---
when I run my application as an app engine web application, in the log console I have that line:
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
console waits about 5-7 second on this line. may be because of "null", what do you think? what is this, and how can I fix that?
I am not using eclipse, using GAE SDK to upload my project, problem is when i am trying to upload it is using jre not jdk thats the reason i am getting below error, please help how can i force app engine sdk to use JDK instead of jre
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\j1013366\Desktop\social.login.2013\appengine-java-sdk-1.8.0\appengine-j
ava-sdk-1.8.0\bin>appcfg.cmd update apps/SocialLoginProject
Reading application configuration data...
Jun 05, 2013 12:22:45 PM com.google.apphosting.utils.config.AppEngineWebXmlReade
r readAppEngineWebXml
INFO: Successfully processed apps/SocialLoginProject\WEB-INF/appengine-web.xml
Jun 05, 2013 12:22:45 PM com.google.apphosting.utils.config.AbstractConfigXmlRea
der readConfigXml
INFO: Successfully processed apps/SocialLoginProject\WEB-INF/web.xml
Jun 05, 2013 12:22:45 PM com.google.apphosting.utils.config.IndexesXmlReader rea
dConfigXml
INFO: Successfully processed apps\SocialLoginProject\WEB-INF\appengine-generated
\datastore-indexes-auto.xml
Beginning interaction for server default...
0% Created staging directory at: 'C:\Users\j1013366\AppData\Local\Temp\appcfg152
7926604447976257.tmp'
5% Scanning for jsp files.
8% Compiling jsp files.
Error Details:
Exception in thread "main" java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.apache.jasper.JspCompilationContext.createCompiler(JspCompilation
Context.java:238)
at org.apache.jasper.JspCompilationContext.createCompiler(JspCompilation
Context.java:214)
at org.apache.jasper.JspC.processFile(JspC.java:1181)
at org.apache.jasper.JspC.execute(JspC.java:1341)
at com.google.appengine.tools.development.LocalJspC.main(LocalJspC.java:
40)
Caused by: java.lang.NullPointerException
at com.google.appengine.tools.development.LocalJspC$LocalCompiler.<clini
t>(LocalJspC.java:53)
... 7 more
com.google.appengine.tools.admin.JspCompilationException: Failed to compile jsp
files.
Unable to update app: Failed to compile jsp files.
Please see the logs [C:\Users\j1013366\AppData\Local\Temp\appcfg5225288314554557
20.log] for further information.
C:\Users\j1013366\Desktop\social.login.2013\appengine-java-sdk-1.8.0\appengine-j
ava-sdk-1.8.0\bin>
Personally I have intentionally set it up to use the JRE from within the SDK by modifying appcfg.cmd to
"%JAVA_HOME%\bin\java" -Djava.home="%JAVA_HOME%\jre" -Xmx1100m -cp "%~dp0\..\lib\appengine-tools-api.jar" com.google.appengine.tools.admin.AppCfg %*
and setting JAVA_HOME to point to the JDK.
I am guessing you could modify -Djava.home="%JAVA_HOME%\jre" to point to wherever you like.
Got this error. Any idea how to get rid of it?
Yesterday it was working fine but today I got these errors. I saw a known issue with this - link. But I didn't find any solution yet..
Oct 16, 2012 4:01:59 PM com.google.appengine.tools.info.RemoteVersionFactory getVersion
INFO: Unable to access https://appengine.google.com/api/updatecheck?runtime=java&release=1.7.1×tamp=1345058163&api_versions=['1.0']
java.net.UnknownHostException: appengine.google.com
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:195)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:559)
at com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:141)
at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:395)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:530)
at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272)
at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:911)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1172)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
at java.net.URL.openStream(URL.java:1010)
at com.google.appengine.tools.info.RemoteVersionFactory.getVersion(RemoteVersionFactory.java:76)
at com.google.appengine.tools.info.UpdateCheck.checkForUpdates(UpdateCheck.java:99)
at com.google.appengine.tools.info.UpdateCheck.doNagScreen(UpdateCheck.java:174)
at com.google.appengine.tools.info.UpdateCheck.maybePrintNagScreen(UpdateCheck.java:142)
at com.google.appengine.tools.development.DevAppServerMain$StartAction.apply(DevAppServerMain.java:289)
at com.google.appengine.tools.util.Parser$ParseResult.applyArgs(Parser.java:48)
at com.google.appengine.tools.development.DevAppServerMain.<init>(DevAppServerMain.java:249)
at com.google.appengine.tools.development.DevAppServerMain.main(DevAppServerMain.java:225)
Oct 16, 2012 4:01:59 PM com.google.apphosting.utils.jetty.JettyLogger info
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Oct 16, 2012 4:02:00 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed D:\WorkSpace\GAE\GST\war\WEB-INF/appengine-web.xml
Oct 16, 2012 4:02:00 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed D:\WorkSpace\GAE\GST\war\WEB-INF/web.xml
Oct 16, 2012 4:02:02 PM com.google.appengine.tools.development.DevAppServerImpl start
If you are using Java 8 in your app engine application, you will need to include
<url-stream-handler> urlfetch </ url-stream-handler>
in appengine-web.xml.
appengine-web.xml Reference
I am assuming that you are seeing this in your Eclipse IDE when you are trying to run the Eclipse Project as a Web Application.
The GAE plugin simply checks if there is an updated AppEngine SDK available for download. If there is a newer one than the one you are currently using then it lets you know that. The error is because at that instance, there was probably a network error and it got not connect through. It is harmless as far as running your application is concerned.
But if your application is dependent on accessing some external network services, then chances are that they might fail also if the network issue persists in your development environment.
got it working.. : cmd->goto your home directory >mkdir .appcfg_no_nag this will stop checking for the update and yourweb app willrun locally atleast..
This error is related to internet connection. I changed to other connection, it works
You should add in appengine-web.xml:
<url-stream-handler> urlfetch </ url-stream-handler>
And also start using java.net.URLConnection,
Apache HttpClient is not gonna work for example.
https://cloud.google.com/appengine/docs/standard/java/issue-requests#java_8_runtime_vs_java_7_behavior
I need to upload a jruby web application to appengine, so I use these commands:
cd my/app/path
jruby -S appcfg.rb update .
This throws an error saying:
Found a file too large to upload: "/var/folders/Qv/QvM5YWsvGP84UoFhrVmLyE+++TM/-Tmp-/appcfg5196464172432329417.tmp/vendor/gems/jruby/1.8/cache/jruby-jars-1.6.0.gem". Must be under 10000000 bytes.
Browsing around I found that I need to pass a --enable_jar_splitting flag like this:
jruby -S appcfg.rb
--enable_jar_splitting update .
Still this command fails, with a different error:
INFO: Opening new file: /var/folders/Qv/QvM5YWsvGP84UoFhrVmLyE+++TM/-Tmp-/appcfg7137125152681466424.tmp/WEB-INF/lib/jruby-core-1.6.0-0000.jar
Apr 11, 2011 1:08:12 PM com.google.appengine.tools.util.JarSplitter run
INFO: Closing file after writing 9991985 bytes.
Apr 11, 2011 1:08:12 PM com.google.appengine.tools.util.JarSplitter createOutFile
INFO: Opening new file: /var/folders/Qv/QvM5YWsvGP84UoFhrVmLyE+++TM/-Tmp-/appcfg7137125152681466424.tmp/WEB-INF/lib/jruby-core-1.6.0-0001.jar
Apr 11, 2011 1:08:13 PM com.google.appengine.tools.util.JarSplitter run
INFO: Closing file after writing 9990346 bytes.
Apr 11, 2011 1:08:13 PM com.google.appengine.tools.util.JarSplitter createOutFile
INFO: Opening new file: /var/folders/Qv/QvM5YWsvGP84UoFhrVmLyE+++TM/-Tmp-/appcfg7137125152681466424.tmp/WEB-INF/lib/jruby-core-1.6.0-0002.jar
Apr 11, 2011 1:08:14 PM com.google.appengine.tools.util.JarSplitter run
INFO: Closing file after writing 1316596 bytes.
java.lang.IllegalStateException: Found a file too large to upload: "/var/folders/Qv/QvM5YWsvGP84UoFhrVmLyE+++TM/-Tmp-/appcfg7137125152681466424.tmp/vendor/gems/jruby/1.8/cache/jruby-jars-1.6.0.gem". Must be under 10000000 bytes.
Seems like it's splitting something... but it's still failing.
Any ideas?