All developers in my team are experiencing the same issue with the new app engine dev server, which hard crashes when debugging via eclipse. The server runs perfectly in "Run Mode", but in "Debug Mode", it starts up fine, but as soon as you hit it with a request, it hard crashes with nothing logged in the console.
Anyone else getting this issue? And any tips on fixing it?
Related
I have a server/client react app that should be logging in the window from where I launched the app. The client logging in showing in Chrome's dev tools, but the terminal window from where I launched the server app is not showing any output, at least not anymore. I was running Visual Studio Code with the debugger and I was asked a permission to allow debugging, I clicked yes and now no output to the terminal window from which I started the server How can I undo this?
I had several processes running even though the terminal window was not running. I had to kill the processes to allow the console logs to come through.
I have just started working on App Engine and during my first sample run only I faced this issue. I deployed the sample 'Hello App Engine' servlet code locally through Eclipse IDE. After hitting the localhost URL I was able to see the expected message 'Hello App Engine' as well.
Later I changed the message body to be displayed (Hi App Engine) and again deployed the code. Now, when I hit the localhost URL I don't see the updated message body. Instead it shows me the old message (Hello App Engine) only.
I tried refreshing my browser and manually setting the 'Run configuration' but nothing worked. Does anybody have any leads what could be the possible reason? Thanks.
Have you verified you are executing the redeployment correctly?.
To make sure you are not failing in this step you should delete the application completely and redeploy it again
I recently started building applications on Google App Engine. I use an Eclipse plugin to start and stop the server and deploy applications to run on Google App Engine.
I had created a new project and tried to stop and start it as suggested in the tutorials and in Stack Overflow. My old project is still running and hitting the data source successfully. I even removed the old projects from my Eclipse workspace and tried a fresh deploy of the new project with no luck.
How do I stop the server (the RED dot in my Eclipse has no effect)? Is uninstalling the App Engine the only solution?
When you launch the server, a new Java process is started. You can find and kill it independently of Eclipse.
I too ran into this problem and found the solution at Stop or restart a previously started Google App Engine local server in Eclipse
Just in case the link breaks, the key steps are:
In Eclipse, find the Eclipse Console view (looks like below).
Select the arrow next to the small computer and find the server's name
Select the red square to stop the server
Go to http://localhost:8888 to see if the page is still showing (it shouldn't be)
If you are visiting something like http://yourAppId.appspot.com and the server is still running, that's because it's still deployed on App Engine, not locally. In this case, go to Google Developer's Console and stop the service there
The server can be stopped by clicking red square icon in the console window. If this icon is missing or disabled, you may see wrong console window. You must select the javaw console using the drop-down button on the far right of the console window.
Go to Run/Debug Configurations -> Select your project configuration -> Common tab -> Uncheck "Launch in background"
Now, when you terminate the server on Server's console, it will stops the server.
I deployed my app successfully on GAE (Java), and the thing works as expected under Chrome (and others) under MacOS X. Today at work I wanted to test my app on IE 9.0.8 / Vista, and the app won't load.
My app displays a "loading" message on the page until all objects of the UI are loaded. When I load the UI I also fetch some data using RPC. When the job gets done the loading message disapears and my app shows up.
As I don't see any error or Exception / nothing special in the app engine logs, how can I start to find the bug ?
The only difference I see is that, at work, my computer goes online trough many firewall and proxys, but as i can open the page and login it should not be a problem. But anyway, just after I login (using google accounts, not openID) the app "hangs". Ideas ?
You should start by inspecting network connections in IE9 to see if everything loads as expected. See also GWT tricks for IE9.
Try running your GWT app in dev mode, this way you should be able to see the client-side errors in the GWT console. Client-side error messages are not displayed in Web mode, unless you implemented code to handle them.
I'm trying to get a silverlight program to install locally and still be able to access wcf data services over ssl. When I run the application in browser, everything works fine. When I run the application out of browser without ssl everything works fine. When I run the application OoB with ssl, I get a "Not Found" error. When I run fiddler and retry, everything works fine. I'm guessing that the program isn't correctly decrypting or sending the ssl traffic when OoB since when fiddler does it for it, the application works fine. I'm also not hitting any exceptions or break points on the server when I attach VS to it (this makes me think there is a problem with the send). Any ideas on what my next step should be? Also, I am using a self signed certificate, could this be an issue? THANKS!
Has anyone found a resolution for this issue? Or does silverlight just not work with SSL in OOB mode??
See this link for reference:
http://msdn.microsoft.com/en-us/library/dd920295(v=vs.95).aspx
basically it says:
Client certificates are supported by the browser stack, but not by the
client stack. And there is currently an issue that (at least for our
application) prevents client certificates from working even with the
browser stack if you're in trusted out-of-browser mode.