We Keep Coding

Why does Google Cloud Tools Plugin for Eclipse say "No Projects Found"?

I'm migrating from Java7 to Java8 and from the old GAE plugin to the new Cloud Tools plugin.
I think I've got it mostly set up correctly - but when I try and run the app I get a 403. And when I look at the Google Cloud Platform section of the Properties the only option is "App Engine Deployment" and when I open that it tells me "No Projects Found".
I'm signed in to Google in Eclipse. When I look at https://console.cloud.google.com/cloud-resource-manager it shows me two projects (one of which is the correct one).
The console shows the following:
2017-12-31 18:40:37.513:INFO::main: Logging initialized #2741ms
2017-12-31 18:40:38.073:INFO:oejs.Server:main: jetty-9.3.18.v20170406
2017-12-31 18:40:41.859:INFO:oeja.AnnotationConfiguration:main: Scanning elapsed time=3321ms
2017-12-31 18:40:42.498:INFO:oejsh.ContextHandler:main: Started c.g.a.t.d.j.DevAppEngineWebAppContext#25bcd0c7{/,file:///C:/Users/andre_000/eclipse-workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/Postr/,AVAILABLE}{C:\Users\andre_000\eclipse-workspace\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\Postr}
2017-12-31 18:40:42.520:INFO:oejs.AbstractConnector:main: Started NetworkTrafficSelectChannelConnector#5db4c359{HTTP/1.1,[http/1.1]}{localhost:8080}
2017-12-31 18:40:42.522:INFO:oejs.Server:main: Started #7751ms
Dec 31, 2017 6:40:42 PM com.google.appengine.tools.development.AbstractModule startup
INFO: Module instance default is running at http://localhost:8080/
Dec 31, 2017 6:40:42 PM com.google.appengine.tools.development.AbstractModule startup
INFO: The admin console is running at http://localhost:8080/_ah/admin
Dec 31, 2017 6:40:42 PM com.google.appengine.tools.development.DevAppServerImpl doStart
INFO: Dev App Server is now running
What am I missing?

Your console output is from the development app server, a local emulator that runs on your development machine (http://localhost:8080). You can use this emulator for debugging your app. Once you're happy with your app, you then deploy it to App Engine which then makes your app available through .appspot.com.

Where can I find the exception stack traces in OpenShift Tomcat Cartridge

So I deployed a WAR file containing my jHipster app (Angularjs+Spring boot) on openshift Tomcat 7 Cartridge. I can open reach my application with no problems (the front end) but once I try to login (interaction with the backend) i get an error.
Normally I check the exception stacktrace in the console of Eclipse IDE if I am debugging my application locally.
I checked the logs in app-root/logs/jbossews.log but I only see that my app is deployed logs. like :
INFO: Deploying web application archive /var/lib/openshift/57582f677628e108ba000096/app-root/runtime/dependencies/jbossews/webapps/ROOT.war
Jun 10, 2016 10:43:18 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive /var/lib/openshift/57582f677628e108ba000096/app-root/runtime/dependencies/jbossews/webapps/ROOT.war has finished in 29,121 ms
Jun 10, 2016 10:43:18 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-127.8.28.129-8080"]
Jun 10, 2016 10:43:18 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 29501 ms
Not my application exceptions.
Is there any configuration that I should add to get my application exceptions in the logs ?

Hard to tell without seeing your configuration but there is a "OPENSHIFT_LOG_DIR" environment variable in every Openshift gear and you can use that to write your log files to the designated log directory.
Example in your spring-boot application.yml file, you can add
logging:
path: ${OPENSHIFT_LOG_DIR}
file: myApplication.log

Cannot run JAX-WS Java Web Service on Apache Tomcat

Summary
I've been tasked to write a Java web service to integrate two disparate systems in our enterprise environment. Since I'm actually an experienced C#.NET MVC developer and only consider myself intermediate at Java, I began by searching for "Java Web Service Tutorials". I am trying to run this common tutorial, but I'm unable to run the tutorial service due to an HTTP 404 error.
Process
I'm using the Java Web Application template in Netbeans 8.0.2. I used JDK 1.6.0.25 to compile the tutorial (since the eventual service I need to write will need this Java version to be compatible with some other JARs I'll be using). Everything compiles to a WAR file just fine.
I then deployed the WAR file by loading the server's Tomcat Manager GUI and using the WAR file to deploy feature. When I do so, the WAR file is copied, and the application starts. However, when I attempt to access the service via the link "http://localhost:8080/HelloWorld/hello" from the tutorial, the service returns a 404 error.
Server Environment
Oracle Enterprise Linux distro, version 3.8.13-44.1.1.el6uek.x86_64
Apache Tomcat 6.0.24
JVM 1.7.0_75-mockbuild_2015_01_20_16_42-b00
If the advice is that I need to change the Java or Tomcat versions or platforms, I need to know that as well since I have little experience with these technologies. However, I may not be able to change all the factors due to limitations with my Linux distro (per my server admin).
Things I've tried (in order):
Setup a Local Tomcat Server on Windows
I installed a local Tomcat Server on my Windows 7 laptop. Since the Linux server is running Java 1.7.0.75, I installed a matching Windows version of JRE 1.7.0.75 from Oracle's support page. I then downloaded Apache Tomcat 6.0.24 Windows Service from their archives and installed it successfully, using the JRE 1.7.0.75 and local port 1985 (to separate it from the GlassFish local server used within Netbeans).
Just as on the Linux server, my local Tomcat server couldn't start the tutorial. Manually clicking the start command link gives me the message "FAIL - Application at context path /com.mkyong.ws could not be started". My local server's logs don't show anything about that application failing to start either.
Adding JAX-WS RI JAR files to {$Tomcat}/lib
Per section 5 on the tutorial mentioned above, I then added the indicated JAR files to the server's {$Tomcat}/lib folder and restarted the server. This time, the application started, but I still couldn't access the service. The link "http://localhost:8080/HelloWorld/hello" from the tutorial returns a 404 error. I even tried copying the entire JAX-WS RI/lib folder to the {$Tomcat}/lib directory with no changes, so I backed out this change.
For reference, here's a list of the files I've copied:
gmbal-api-only.jar
ha-api.jar
jaxb-core.jar
jaxb-impl.jar
jaxws-api.jar
jaxws-rt.jar
management-api.jar
policy.jar
stax-ex.jar
streambuffer.jar
Enabling DEBUG mode in the local Tomcat Server
I un-deployed the WAR file. Using the Apache Tomcat Monitor, I stopped the service, deleted the existing logs, enabled the DEBUG logging level, and restarted the service. I then re-deployed the tutorial WAR file. I again saw it didn't start, and then I opened all the log files. There is not even a mention of the failure to access the service, but perhaps 404 errors aren't logged.
Running the service using the Netbeans-embedded Glassfish server
When I first created the Web Application, Netbeans offered to set me up with a local Glassfish server. I accepted, and I set everything up with defaults. When I try to run the tutorial against this server, I cannot access the service. The link "http://localhost:8080/HelloWorld/hello" from the tutorial still returns a 404 error.
Researching other posts and tutorials
Here are some other StackOverflow posts and websites I've reviewed without finding a resolution:
JAX-WS on Tomcat server (doesn't apply)
Deploying JAX-WS webservice as War in Apache Tomcat (similar to the tutorial in recommending to copy the extra JAR files)
JAX-RPC / JAX-WS runtime in Apache Tomcat (just informational)
how to deploy a jax-ws service to eclipse or tomcat? (similar to the tutorial in recommending to copy the extra JAR files)
https://myarch.com/create-jax-ws-service-in-5-minutes/ (similar to the tutorial but without deployment help)
Questions I'm Pondering
Is there something wrong with the code in the tutorial? (Doesn't seem likely since from the comments others have had success.)
Is there a significant difference in the versions of Java or Tomcat he's using in the tutorial? (He doesn't give an versions of Java or Tomcat.)
Should I run local Tomcat against a JDK instead of a JRE?
Should the tutorial be compiled against the same JDK as Tomcat is using? (I hope not as this would seem very limiting...)
Can I even run JAX-WS in Tomcat? (Based on pages like http://tomee.apache.org/apache-tomee.html, it seems like the base TOmcat might not even support JAX-WS? Again, just my limited experience.)
I'd appreciate any troubleshooting guidance anyone can offer. Thank you in advance for the help!
UPDATE #1
Per the request of #NIKETBHANDARY, I stopped the service, deleted the logs, restarted the service, and browsed in Chrome to localhost:1985/helloworld/hello - still getting the 404 error. I then opened the catalina.log file, but it's completely empty. Only jakarta_service.log has any log entries, and all are about the service starting. I also verified that the logging level is set to debug. What else can I change to get additional log messages?
I also ran a search for "com.mkyong" in the entire Tomcat directory. Only the webapp WAR file, webapps/../META-INF/context.xml, webapps/../WEB-INF/sun-jaxws.xml, and /conf/cataline/localhost/com.mkyong.we.xml files returned any hits. Nothing in any logs. Could that indicate that this is a configuration problem?
UPDATE #2
Apparently, Tomcat doesn't flush its log messages fully until the thread closes as the service shuts down (probably due to the logging configuration). As such, I stopped the service which flushed the log files. Here's the entire contents of the catalina.log file (which does contain a reference to com.mkyong):
Aug 17, 2015 9:51:17 PM org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.19.
Aug 17, 2015 9:51:17 PM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
Aug 17, 2015 9:51:19 PM org.apache.coyote.http11.Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-1985
Aug 17, 2015 9:51:19 PM org.apache.coyote.ajp.AjpAprProtocol init
INFO: Initializing Coyote AJP/1.3 on ajp-8009
Aug 17, 2015 9:51:19 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2121 ms
Aug 17, 2015 9:51:19 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Aug 17, 2015 9:51:19 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.24
Aug 17, 2015 9:51:19 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor com.mkyong.ws.xml
Aug 17, 2015 9:51:20 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
Aug 17, 2015 9:51:22 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing
Aug 17, 2015 9:51:22 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
Aug 17, 2015 9:51:22 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor manager.xml
Aug 17, 2015 9:51:22 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory docs
Aug 17, 2015 9:51:22 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory examples
Aug 17, 2015 9:51:22 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
Aug 17, 2015 9:51:22 PM org.apache.coyote.http11.Http11AprProtocol start
INFO: Starting Coyote HTTP/1.1 on http-1985
Aug 17, 2015 9:51:22 PM org.apache.coyote.ajp.AjpAprProtocol start
INFO: Starting Coyote AJP/1.3 on ajp-8009
Aug 17, 2015 9:51:22 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 3895 ms
UPDATE #3
I'm becoming more convinced there's a configuration problem somewhere. On a hunch, I studied and installed Apache TomEE 1.7.2 for Windows, pointing to the same JRE as the regular Tomcat. After studying the running.txt file and experimenting with the properties and settings, I was finally able launch a local version of TomEE. I deployed the same WAR file as before, and I found it would not load the WAR application due to the following error:
java.lang.ClassNotFoundException: com.sun.xml.ws.transport.http.servlet.WSServletContextListener
Googling that error led (again) to MKYong's blog for a fix (copy the jaxws-rt.jar file to the {$tomcat}/lib folder. I redeployed the WAR file, and the manager loaded the application. HOWEVER, just like on regular Tomcat, the URL "http://localhost:8080/HelloWorld/hello" from the tutorial still returns a 404 error. So, the results are exactly the same.
Short of compiling the tutorial against other versions of JDK, I'm running out of ideas quickly... :-)
UPDATE #4
Per another request below, here's a list of all JAR files in the {$Tomcat}\lib folder:
annotations-api.jar
catalina.jar
catalina-ant.jar
catalina-ha.jar
catalina-tribes.jar
el-api.jar
gmbal-api-only.jar
ha-api.jar
jasper.jar
jasper-el.jar
jasper-jdt.jar
jaxb-core.jar
jaxb-impl.jar
jaxws-api.jar
jaxws-rt.jar
jsp-api.jar
management-api.jar
policy.jar
servlet-api.jar
stax-ex.jar
streambuffer.jar
tomcat-coyote.jar
tomcat-dbcp.jar
tomcat-i18n-es.jar
tomcat-i18n-fr.jar
tomcat-i18n-ja.jar
The {$Tomcat}\webapps folder contains the following:
..\com.mkyong.ws
..\docs
..\examples
..\host-manager
..\manager
..\ROOT
..\com.mkyong.ws.war
Update #5
The {$Tomcat}\webapps\com.mkyong.ws directory contains the following:
Here's a screenshot of the Tomcat Manager GUI:
Here's a screenshot of the HTTP 404 error I'm receiving along with the URL:
I've also confirmed that the files in the WAR exactly match the tutorial.

There is problem in deployment of your ws module.
U have just copied the whole folder from the MKyoung sample.
I doesn't work that way around.
Not only that now display all the folders and files structure inside the ws module delete the rest of the modules from your post.I wanted only the structure of ws module.
The module name has to sample instead of com.mkyoung.ws
and the structure for it has to be
**sample**
------WEB-INF
------index.jsp
WEB-INF
----classes
----web.xml
----sun-jaxws.xml
classes
----com
--------mkyoung
-----------ws
ws
-----Helloworld.class
-----HeloworldIMPL.class

#NIKETBHANDARY helped me understand what was wrong and how to quickly correct it. I'd also like to post exactly what I did wrong and how I fixed it permanently so that future coders can benefit from my five-day experience. :-)
When I originally built the tutorial using Netbeans, I used the Java Web --> Web Application template (which is available after installing the Java EE Base plugin accessible through Netbeans --> Tools --> Plugins):
I built all the files exactly per the tutorial, but I failed to really read through step #5, especially this line:
<jar jarfile="${dist}/war/HelloWorld-${DSTAMP}.war" basedir="${dist}/war/build/"/>
After further review, I found that the build script was producing a WAR file called HelloWorld.war. Then, when that file was deployed to Tomcat, the web application was called HelloWorld in the Tomcat Manager. That's why the service endpoint was set to http://localhost:8080/HelloWorld/hello. The "HelloWorld" is literally the name of the Tomcat application, and the "/hello" part corresponds with the endpoint from the sun-jaxws.xml file. (Looking back, it makes total sense given typical web hosting organization. IIS pretty much works the same way.)
So, to fix the problem, I needed to modify the Netbeans project to produce a WAR file named HelloWorld.war. In the tutorial, he includes an actual Ant build script. In this case, I needed to take these steps:
Right-click on the project in the Netbeans Project Explorer.
Choose Properties.
Click on the Build --> Packaging category.
Set the WAR file field to HelloWorld.war.
Here is a screenshot:
Once that was done, I created a new build, deployed to my local Tomcat server, and everything worked as expected. I was also able to deploy the WAR file to my Linux server and test it successfully. Problem solved! :-)

Cannot open http://localhost:8080/ when Tomcat is running in Eclipse

I got the same problem with the questions here : Tomcat started in eclipse but unable to connect to link to http://localhost:8085/, that means I can't open http://localhost:8080/ at the browser :
HTTP Status 404 - /
type Status report
message /
description The requested resource (/) is not available.
Apache Tomcat/7.0.27
//Console info when tomcat started//
Apr 10, 2012 4:26:32 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to org.eclipse.jst.jee.server:SimpleServletProject' did not find a matching property.
Apr 10, 2012 4:26:32 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Apr 10, 2012 4:26:33 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Apr 10, 2012 4:26:33 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 880 ms
Apr 10, 2012 4:26:33 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Apr 10, 2012 4:26:33 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.27
Apr 10, 2012 4:26:33 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Apr 10, 2012 4:26:33 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Apr 10, 2012 4:26:33 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 495 ms
I'm using Tomcat 7.0.27, Eclipse Europa and Java 1.6.0_32. I saw BalusC's answer, but the problem is that I couldn't select Tomcat installation (the picture below).
What could be wrong here?
EDIT1 : When I tried to create demo webpage, it couldn't be opened too (with the same error).
EDIT2: Followed this thread Why tomcat server location property is greyed in Eclipse I can open http://localhost:8080/ in the browser, but still cant access the demo web page..
<?xml version="1.0" encoding="UTF-8"?>
<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" id="WebApp_ID" version="2.5">
<display-name>SimpleServletProject</display-name>
<welcome-file-list>
<welcome-file> index.html</welcome-file>
</welcome-file-list>
</web-app>
PS : It seems that there's no more space to me to post index.hmtl (it's just a normal html )..

I am using apache 7. When started in command prompt everything works as expected but if I start same from eclipse then I was not able to access it and find the settings.
Looks like eclipse uses by default 'Use workspace metadata' and deploy path to 'wtpwebapps' in server settings. Follow the below steps to change these and you will be able access localhost:8080 when you start server in eclipse.
In eclipse servers tab at bottom, right click, where you can see start, stop etc, and select properties.
In properties window, select general, then select Switch Location.
Now you can see Tomcat v7.0 Server at localhost in the servers tab, double click on it.
a. If there are any modules deployed, temporarily remove them and close out tab to save this change, otherwise go directly to step 4c below.
b. If you removed any modules, restart server after step 4a and proceed to step 4c.
c. In server location, select radio button 'Use tomcat installation', and select 'webapps' in deploy path.
Save and start server in eclipse. Now you will be able to access the server.

You want to access the root application (http://server:port/) but I'm quite sure that Eclipse wont install a root application. Try to access the application you deployed within the (eclipse managed) tomcat under http://server:port/yourapp.

In eclipse servers tab at bottom, right click, where you can see start, stop etc, and select properties.
****This works fine:****
In properties window, select general, then select Switch Location.
Now you can see Tomcat v7.0 Server at localhost in the servers tab, double click on it.
a. If there are any modules deployed, temporarily remove them and close out tab to save this change, otherwise go directly to step 4c below.
b. If you removed any modules, restart server after step 4a and proceed to step 4c.
c. In server location, select radio button 'Use tomcat installation', and select 'webapps' in deploy path.

Please check your sample application request context path.

It seems you want to connect to the same port as eclipse (8080). same as running skype and running a server will by default clash because they want to send data through the same port.
Try configurating the server connection ports you might want to set the localhost to port 3000 and try if that works.

google app engine service unavailable

I'm was following http://googcloudlabs.appspot.com/ tutorial to create new Google App Engine project. It throws me an error as per below when I try to run the from my local host, but when I deployed it working fine. (http://mynewcloudcom.appspot.com/). Please help.
HTTP ERROR: 503
Problem accessing /. Reason:
SERVICE_UNAVAILABLE
Powered by Jetty://
Eclipse Console
Mar 05, 2012 10:42:46 AM com.google.apphosting.utils.jetty.JettyLogger info
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Mar 05, 2012 10:42:46 AM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed C:\Smartag_Eclipse_Project\DontEditProject\war\WEB-INF/appengine-web.xml
Mar 05, 2012 10:42:46 AM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed C:\Smartag_Eclipse_Project\DontEditProject\war\WEB-INF/web.xml
Mar 05, 2012 6:42:48 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The server is running at http://localhost:8888/
Mar 05, 2012 6:42:48 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The admin console is running at http://localhost:8888/_ah/admin

Found the answer. I need to run in JDK1.6. Once i changed the Java Compiler(right click project -> properties -> Java Compiler -> (Check) Enable project specific settings -> change the Compiler compliance level), its works fine now. Thanks.

I had the same problem. I justed changed the port from 8888 to 80 in the Debug Configuration and it worked for me.

I had the same issue.
for me the problem was one of my filters had an exception. specifically objectify - it was not loaded properly. you can delete the filter and see if that's it

When using Java 1.7, also check for the Execution Environment and set it to JavaSE-1.7.
You can look into the Execution Environment in:
Right Click -> Properties -> Java Compiler
And you have the option above Restore Defaults and Apply.

I faced the same issue and resolved it by selecting "Automatically select an unused port" in run configuration.

Sometimes it happens there is a "hanging" process that blocks the port. Therefore changing port in Run configuration helps, as well as checking "Automatically select an unused port" in run configuration.

It happened with me too. In my case, I had Run the project and due to some error in my code, the Project ran with errors. So, I debugged it and Run it again but without cancelling the earlier one in the console and it gave me that error. After cancelling or stopping the Project, it ran fine.

i had the same issue. Seems that Plugin is stocked on creating and opening the socket for the server. i don't really know why happens, I've resolved in this way.
Open Run Configurations.
Open Server tab. Change the Embedded server Port.
Open Arguments tab.
3.1 - VM arguments box. i've deleted all that stuff there and just let this
line and save changes and run it.
-Xmx512m -javaagent:/Applications/eclipse/plugins/com.google.appengine.eclipse.sdkbundle_1.7.5/appengine-java-sdk-1.7.5/lib/agent/appengine-agent.jar
It has worked pretty good 4me.
If someone know which events or configuration change are the reason for . please let us know it
NOTE: "I'm not responsible for unexpected behave. I'm don't know if there is side effects ahead"

The solution working for me is to run appEngineServer from command line using Gradle, as comments in generated build.xml for endpoints module proposes. And gradle config includes option for Java 1.7 compatibility, so it's no reason to use Java 1.6 if You want 1.7:
gradlew modulename:appengineRun
Currently, the appengine gradle plugin's appengine devappserver
launch doesn't interact well with Intellij/AndroidStudio's
Gradle integration. As a temporary solution, please launch from the command
line. ./gradlew modulename:appengineRun

I had a condition where a servlet defined in the web.xml with non existent class name. I specified proper class name, worked!