GWT development mode. Unable to load module in Chrome.

I am trying to download my application in development mode using Chrome v. 20.0 on my local ip 127.0.0.1. The application does not load, and the following is displayed:

  • message: "The GWT code server is disconnected. Most likely you closed GWT Development Mode. Or, you may have lost your network connection. To fix this, try restarting GWT Development Mode and REFRESH on this page.

  • on top of the previous message (superimposed): "The plugin could not connect to the development mode server at 127.0.0.1:9997 Follow the troubleshooting instructions"

It started about 6-9 months ago and after updating 1 or 2 pages, the module loaded correctly. Now I can’t load my application in dev-mode in general using Chrome. (everything is fine in Firefox). I am using GWT 2.4

UPDATE:

These errors are not accompanied by the exit of the code stack trace. Usually, if I changed the address form 127.0.0.1 to localhost, the module loaded, but this no longer works ...

+7
source share
6 answers

Take a look at http://code.google.com/p/google-web-toolkit/wiki/TroubleshootingOOPHM

This page should be displayed in the iframe below the message (hence the message "basic instructions", but Google has changed the server code to code.google.com , and now they prohibit displaying inside iframes, so it actually does not work

FYI, the problem was detected in the GWT tracker http://code.google.com/p/google-web-toolkit/issues/detail?id=7301

+1
source

There was the same problem. Removing / reinstalling the plugin did the trick for me.

+3
source

Check Automatically select an unused GWT port from the startup configuration. My similar problem is solved by this

+2
source

I solved this in chrome:

  • go to chrome: // extensions /
  • find the GWT Developer Plugin
  • uncheck Enabled
  • check the Enabled box
+2
source

Your problem may be caused by incorrect configuration of the gwt plugin. Go to the gwt developer plugin settings (red top toolbar connector) in chrome and add the web server addresses and server code. It worked for me.

0
source

Allow "localhost" as a web server and code server to make it work for me (although 127.0.0.1 was specified as for the browser)

0
source

All Articles