I'm running a small scala Play application in dev mode on a vagrant box using activator run. When accessing the app from the browser some of the requests hang for what looks like indefinitely.
This seems to be the same issue as described in this question for play 2.0 Play Framework Hanging when hitting app in browser. The solution suggested there however doesn't seem to apply to the latest version of play.
I'm not sure where to start investigating this issue. Any help will be appreciated!
So after investigating it for a bit we realised that requests hang on routes that were protected by deadbolt. After replacing deadbolt all went back to normal. We were using deadbolt-scala 2.5.0 if anyone has any idea what might have been the issue there a comment here would be welcomed. But for now we stopped using the library.
Related
I've recently deployed a Unity application to the web using WebGL. I have Sentry integrated on the frontend logging exceptions, and I've added the Sentry SDK to Unity. The frontend seems to log no problem, however Unity seems to be struggling. Sometimes I'll get errors reported but a lot of the time I don't. To my knowledge there's no explicit onerror callback I can hook into. I've tried catching the exception in managed code and then reporting that to the frontend, but that doesn't seem to work either.
Any help would be appreciated
I recently began using GWT 2.7 in Eclipse Luna and I was running my projects seamlessly while testing them in localhost:8888, the thing is, when I tried to test them (any of them, even a new app with only the autogenerated content) with another device on the same local network using (pc running eclipse ip):8888 I get a message like this:
The page at (ip):8888 says: Couldn't load (app) from Super Dev Mode server at http://(ip):9876. Please make sure this server is ready. Do you want to try again?
This also happens when I try to access to the app in the pc running eclipse with (its own ip):8888.
I've checked these four similar questions, but they didn't have any really helpful answers, these are a few things I've tried or discovered already:
I enabled the 9876 port on the firewall
I've deleted the .nocache.js and .devmode.js so that they're generated again
I noticed that when this problem occurs it's because the browser can't get the (ip):9876/recompile-requester/(app) file
I tried deploying the app to GAE and it doesn't work there either, nothing that happens on the modules Java code runs (And for some reason, I get a "Uncaught java.lang.ClassCastException" message on the chrome console, but this only happens on the deployed version, it doesn't happen on localhost:8888 or in (local ip):8888)
But nothing has worked and the four questions I mentioned are pretty much the only things related to this I've found, so I really don't know what else to try.
As Thomas pointed out, the problem I had was that from GWT 2.6 onwards, if you want to test from other devices in the same network, you have to whitelist the addresses you'll be using in each *.gwt.xml file using a command line like this:
<set-configuration-property name="devModeUrlWhitelistRegexp" value="http://(localhost|127\.0\.0\.1|192\.168\.150\.(\d{1,3}))(:\d+)?/?.*" />
I also had to add a -bindAddress 0.0.0.0 attribute to the run config for it to work.
I just upgraded to the App Engine 1.7.6 SDK for my python app and realised that breakpoints no longer work in PyDev (Eclipse plugin) when using the new dev_appserver.py.
Does anyone know of a way of enabling them again? I assume the new server is spawning a new process for the web server, and the debugger isn't attaching to that one. I'm not sure how to configure it to do that though.
In the meantime I am using the old_dev_appserver.py server.
UPDATE 2012-07-27:
Following the comment, I verified, the issue is solved after updating to
PyDev. 2.8 and App Engine 1.8.2
OBSOLETE:
I found the following analysis of the problem at googleappengine issues tracker
The reason why PDB doesn't work is because dev_appserver is using
stdin/stdout for interprocess communication. Python has built-in
libraries for IPC: http://docs.python.org/2/library/ipc.html.
dev_appserver should use these, and then stdin/stdout can be left
alone so that PDB still works.
So it seems that there is no workaround, rather than reverting to use old_dev_appserver.py
UPDATE 2013-04-23:
Inability to debug is annoying.
Many developers complain about it
PyDev Breakpoints in App Engine 1.7.6 broken?
https://groups.google.com/forum/?fromgroups=#!topic/google-appengine/ep5BWYKpQpU
https://groups.google.com/forum/?fromgroups=#!topic/google-appengine/TCQuJpF44cY
https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?id=28
https://code.google.com/p/googleappengine/issues/detail?id=9012
I am keeping track of the development of this issue here:
http://goo.gl/XRU01
Yep, ran into the same problem.
Open your Run/Debug Configuration and set the Main Module to:
${GOOGLE_APP_ENGINE}/old_dev_appserver.py
Do you mean pdb.set_trace() isn't working?
Look for the function MonkeyPatchPdb() in google/appengine/tools/dev_appserver.py
Run that somewehere in your own project before you use pdb and it should fix it.
Whenever I run Google App Engine it seems to be running an older version of the servlet than the last one I've saved.
What's going on? How can I fix this?
I'm using the GAE Eclipse Plugin.
I think this is a common pitfall. I also ran into a couple of times.
You should delete the cookies and the cache from Chrome.
If this isn't working, you should terminate and restart the server at eclipse all the time, when you modify the server side code.
I'm currently working on a project based on Spring 3.1.2 which needs to run over GAE.
After researching the logs, I think I know why I'm getting a 500 Internal Server Error whenever I need to interact with the App. The problem I'm facing is related with ASM (http://asm.ow2.org/).
It seems like GAE relies on ASM 4.0, while the project runs fine locally if I use ASM 3.1.
However, I found impossible to make it work when ASM 4.0 :(
I'm completely new to Google App Engine, so ... any tip to solve this issue is welcome! (I've already lost the whole morning finding what the problem was and trying too many different ways to solve it ... but no way).
Thank you very much in advance for your suggestions ;)
I found some information about that, try to upgrade your spring version to 3.2 M2. This version support cgilib 3.0 with asm 4.0!
Visit https://jira.springsource.org/browse/SPR-9669