App engine "hello world" not working (java) - java

i downloaded the google app engine plugin for eclipse and i opened a new web project.
but when i try to run this project (untouched) the eclipse say:
"The server is running at http://localhost:8888/"
so i opened the browser and i get 101 error
"The connection to localhost was interrupted."
what i did wrong?
here is what the console present:
Dec 21, 2011 12:10:03 AM com.google.apphosting.utils.jetty.JettyLogger info
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Dec 21, 2011 12:10:03 AM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed C:\Users\sl300\Synca\try2\war\WEB-INF/appengine-web.xml
Dec 21, 2011 12:10:03 AM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed C:\Users\sl300\Synca\try2\war\WEB-INF/web.xml
Dec 21, 2011 2:10:04 AM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The server is running at http://localhost:8888/
Dec 21, 2011 2:10:04 AM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The admin console is running at http://localhost:8888/_ah/admin
(little details: i have windows vista, eclipse Helios Service Release 2.
i tried with jre6 or jre7 )

This can occur because of your 'Hosts File Configuration' or 'Proxy settings' or 'Anti-Virus software on your system' or if you are using web-debugging/http-logging tools like Fiddler or TCPMon. Correct the configuration if it is not properly set and try it again.

Related

Getting Selendroid standalone to run, Command 'aapt' was not found inside the Android SDK

I have been trying to work on things using selendroid, but I can't get the standalone to run. I have been trying to run the command "java -jar selendroid-standalone-0.15.0-with-dependencies.jar -app selendroid-test-app-0.14.0.apk". But I just keep getting "SEVERE: Error building server: Command 'aapt' was not found inside the Android SDK....". I already referenced This, but it didn't help.
Paths to Java and Android SDK's
Outputs in the Command Prompt
I realized that the picture was a bit small...
Apr 30, 2015 1:40:41 PM io.selendroid.standalone.SelendroidLauncher main
INFO: ################# Selendroid #################
Apr 30, 2015 1:40:41 PM io.selendroid.standalone.SelendroidLauncher main
INFO: ################# Configuration in use #################
Apr 30, 2015 1:40:41 PM io.selendroid.standalone.SelendroidLauncher main
INFO: io.selendroid.standalone.SelendroidConfiguration#816f27d[
port=4444
timeoutEmulatorStart=300000
supportedApps=[selendroid-test-app-0.15.0.apk]
verbose=false
emulatorPort=5560
deviceScreenshot=false
selendroidServerPort=8080
keystore=<null>
keystorePassword=<null>
keystoreAlias=<null>
emulatorOptions=<null>
keepEmulator=false
registrationUrl=<null>
proxy=<null>
serverHost=<null>
keepAdbAlive=false
maxSession=5
maxInstances=5
noWebViewApp=false
noClearData=false
sessionTimeoutSeconds=1800
forceReinstall=false
logLevel=ERROR
deviceLog=true
serverStartTimeout=20000
printHelp=false
serverStartRetries=5
folder=<null>
]
Apr 30, 2015 1:40:41 PM io.selendroid.standalone.SelendroidLauncher launchServer
INFO: Starting Selendroid standalone on port 4444
Apr 30, 2015 1:40:41 PM io.selendroid.standalone.SelendroidLauncher launchServer
SEVERE: Error building server: Command 'aapt' was not found inside the Android SDK. Please update to the latest development tools and try again.
If I left out any information just let me know.
Thanks
EDIT: Here's the latest
Your ANDROID_HOME environment variable is:
C:\Program Files(x86)\Android\android-skd
Please try to change to:
C:\Program Files(x86)\Android\android-sdk
EDIT: Also check that aapt.exe is inside of platform-tools folder, otherwise copy aapt.exe from the last build tools you have, for example:
<android-sdk>\build-tools\22.0.1\aapt.exe
to:
<android-sdk>\platform-tools\aapt.exe
As Mattai said, Selendroid checks for aapt inside platform-tools.
But I was getting the same error even after copying the appt to platform-tools folder.
But worked when I tried after restarting the system!
Thanks Mattai!

issues while deploying app to google app engine

I am on 1.8.1 GAE for java using eclipse on a mac book pro mountain lion.
On trying to deploy I am getting error:
Unable to update:
com.google.appengine.tools.admin.HttpIoException: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=sakshumweb-hrd&version=3&
409 Conflict
Another transaction by user vik.ceo is already in progress for app: s~sakshumweb-hrd, version: 3. That user can undo the transaction with "appcfg rollback".
at com.google.appengine.tools.admin.AbstractServerConnection.send1(AbstractServerConnection.java:293)
at com.google.appengine.tools.admin.AbstractServerConnection.send(AbstractServerConnection.java:253)
at com.google.appengine.tools.admin.AbstractServerConnection.post(AbstractServerConnection.java:232)
at com.google.appengine.tools.admin.AppVersionUpload.send(AppVersionUpload.java:810)
at com.google.appengine.tools.admin.AppVersionUpload.beginTransaction(AppVersionUpload.java:543)
at com.google.appengine.tools.admin.AppVersionUpload.doUpload(AppVersionUpload.java:135)
at com.google.appengine.tools.admin.AppAdminImpl.doUpdate(AppAdminImpl.java:386)
at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:55)
<dx59b2s3gxmlhdp3940000gn/T/appengine-deploy2012670164492350692.log" 17L, 1449C
I have already executed the below command which succeeds but the deployment still fails with the same error. Please note that in past I have done it without any issues 100s of times.
/Users/vivekkumar/Downloads/Sakshum/eclipse/plugins/com.google.appengine.eclipse.sdkbundle_1.8.1.1/appengine-java-sdk-1.8.1.1/bin/appcfg.sh rollback war
Reading application configuration data...
Oct 11, 2013 9:43:02 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed war/WEB-INF/appengine-web.xml
Oct 11, 2013 9:43:02 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed war/WEB-INF/web.xml
Oct 11, 2013 9:43:02 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed war/WEB-INF/cron.xml
Oct 11, 2013 9:43:02 PM com.google.apphosting.utils.config.IndexesXmlReader readConfigXml
INFO: Successfully processed war/WEB-INF/appengine-generated/datastore-indexes-auto.xml
Beginning interaction for server default...
0% Rolling back the update.
Success.
Cleaning up temporary files for server default...
I was the same issue (without GWT) and i solved deploy 409 error thanks this answer
Try it please, remove instance-class and automatic-scaling elements from appengine-web.xml.
You may need to cut down the number of permutations for the GWT compiler otherwise you'll end up with permutation explosion (the compiler will generate tons of files for each user agent, locale, ...etc), causing a timeout for app engine while deploying your app.
Try : Soft Permutations
OR : Controlling Permutation Explosion

Google App Engine not being accessed via localhost

I am using Mac OS X 10.7.4, app engine sdk 1.7.0, eclipse juno and Java as programming language. The problem is that App runs perfectly well when deployed on appspot but does not work on localhost. When run as web application on port 8888 or any other port (if change it from the configuration), the log represents server is running but when I hit the URL, nothing happens and after some time connection times out. When, debugged it gives the error: Cannot connect to VM. Logs from console for both run and debugged are shown below, kindly help me, I have searched all over the 'net but could not find the solution.
Log when Debugged:
ERROR: transport error 202: handshake failed - connection prematurally closed
ERROR: JDWP: Failed to initialize transport via localhost:49741, trying localhost via 127.0.0.1:49741
ERROR: transport error 202: recv failed during handshake: Connection reset by peer
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Log when run:
2012-07-17 19:07:42.504 java[417:407] [Java CocoaComponent compatibility mode]: Enabled
2012-07-17 19:07:42.505 java[417:407] [Java CocoaComponent compatibility mode]: Setting timeout for SWT to 0.100000
Jul 17, 2012 2:07:49 PM com.google.apphosting.utils.jetty.JettyLogger info
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Jul 17, 2012 2:07:50 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed /Volumes/DATA 1/Google App Engine/Java/HelloWorld/war/WEB-INF/appengine-web.xml
Jul 17, 2012 2:07:50 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed /Volumes/DATA 1/Google App Engine/Java/HelloWorld/war/WEB-INF/web.xml
Jul 17, 2012 7:07:52 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The server is running at localhost:8888/
Jul 17, 2012 7:07:52 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The admin console is running at localhost:8888/_ah/admin
Log when Run from command line:
Jul 21, 2012 3:23:19 PM com.google.apphosting.utils.jetty.JettyLogger info
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Jul 21, 2012 3:23:19 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed /Volumes/DATA 1/Softwares/appengine-java-sdk-1.7.0/demos
/guestbook/war/WEB-INF/appengine-web.xml
Jul 21, 2012 3:23:19 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed /Volumes/DATA 1/Softwares/appengine-java-sdk-1.7.0/demos/guestbook/war/WEB-INF/web.xml
Jul 21, 2012 8:23:22 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The server is running at http://localhost:8080/
Jul 21, 2012 8:23:23 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The admin console is running at http://localhost:8080/_ah/admin
Check the following:
1) If the application has actually started. Enter "ps ax | grep java" in terminal
2) If the application has bound to the port. Install nmap (not sure how to do it on mac) and run it with "nmap localhost". You will see a list of ports and protocols used. If you don't see 8888 with http then something is wrong.
Have you tried running it from the command line? It looks like you're trying to start it in the debugger as well.. no? Try running from the command line, make sure that works. Then try running it from eclipse with "Run" not "Debug" and make sure that works before trying the debugger. Appengine is a little bit particular...

Troubleshoot Eclipse's "Run on server" deploy

I am taking over an existing Struts-based web application and am trying to deploy it for the first time on my local machine. My predecessor told me to run it through Eclipse on a Tomcat server.
I have installed the latest tomcat and it is running fine. I have grabbed the code from their CVS server and, with a few tweaks, removed all of the errors from the Java files. I then created a new Run Configuration having it run as "Run on server".
When I run the Run Config, the tomcat server starts up without error messages in the Console and an Eclipse browser page pops up to the correct local URL. The returned page is a 404, however. Looking at my Tomcat "webaps" folder, I see that my application is not there.
My question is, how can I troubleshoot this? My tomcat error logs do not get updated when I deploy and the Console output, shown below, offers no hint that there is a problem.
May 30, 2011 3:48:07 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: <long list of paths>
May 30, 2011 3:48:07 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
May 30, 2011 3:48:07 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 410 ms
May 30, 2011 3:48:07 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
May 30, 2011 3:48:07 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
May 30, 2011 3:48:08 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor CanPost_Emil.xml
May 30, 2011 3:48:08 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
May 30, 2011 3:48:08 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
May 30, 2011 3:48:08 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/31 config=null
May 30, 2011 3:48:08 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 244 ms
This is not the way to run web apps inside Eclipse.
Go to the Server view panel instead, and choose Add server. Here install the Tomcat adapter according to the instructions, and then add the projects you have (if they are Dynamic Web Projects). You can now start and stop the server and have the projects chosen updated when you change.
Do it this way. Do not try to create a Run Configuration launching Tomcat.
I have exactly the same problem.
While this is not a solution to the problem itself (running the project on Tomcat from within Eclipse), it is a way to run the project:
Pack(age) the project (I use maven: 'mvn clean package')
Copy the .war file into the webapps dir inside your tomcat installation.
(if not already running) Start up tomcat.
This works for me. I'm still looking for the proper answer to your question, but until I find it I'll just continue to manually package/deploy the project.

An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17

I downloaded Apache Tomcat 7.x. When I add this Tomcat in Eclipse I get this error:
Jan 25, 2011 3:21:05 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17
Jan 25, 2011 3:21:05 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17
Jan 25, 2011 3:21:05 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17
Jan 25, 2011 3:21:05 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17
Jan 25, 2011 3:21:05 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17
Jan 25, 2011 3:21:08 PM org.apache.coyote.AbstractProtocolHandler init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Jan 25, 2011 3:21:08 PM org.apache.coyote.AbstractProtocolHandler init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Jan 25, 2011 3:21:08 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 3054 ms
Jan 25, 2011 3:21:08 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jan 25, 2011 3:21:08 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.6
Jan 25, 2011 3:21:08 PM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Jan 25, 2011 3:21:08 PM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Jan 25, 2011 3:21:08 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 251 ms
How can I solve this problem?
When I open the localhost:8080/manager/html it shows the following error:
HTTP Status 404 - /manager/html
type Status report
message /manager/html
description The requested resource (/manager/html) is not available.
Apache Tomcat/7.0.6
The first error certainly sounds like a version mismatch. The APR library is a library linked in at runtime based on your path (which itself can be based on where you execute Tomcat from). It sounds like you have the APR library for Tomcat 6. It's possible that Eclipse is providing this APR library.
Tomcat ships with an APR library but in order to ease installation Tomcat doesn't automatically modify the path to point at the APR library. The Eclipse Tomcat integration may (I'm not sure on this one, haven't used the integration before) include the APR libraries to make it easier to use Tomcat.
Check and make sure that Eclipse isn't configured to use an earlier version of Tomcat and if it is, either upgrade Eclipse to Tomcat 7 or downgrade Tomcat to the version specified in Eclipse.
If you can't figure it out then you don't necessarily have to worry about it at the moment. Tomcat should work anyways without the APR libraries. The only benefit you will get from the APR libraries is increased performance and since this is probably the start of your project that doesn't have to be worked out right away.
The second issue, the /manager/ page, could be Tomcat configuration. Tomcat won't actually display the manager page (and it will give you that error) unless users have been configured with manager permissions.
Try going to just / (i.e. http://localhost:8080), that page should load regardless of user configuration.
In my case I had inadvertently installed the APR library when I install once Tomcat locally on my Linux using the package manager. On Debian/Ubuntu this installed the APR package for a different Tomcat version (the one bundled with your distribution) which caused this error.
After simply
sudo apt-get purge libtcnative-1
The error was gone.

Categories