GWT 2.0.2 : Failed to Connect 127.0.0.1:8888 development mode

[Thomas]

Hi,
I followed the steps on http://code.google.com/webtoolkit/usingeclipse.html
and updated my eclipse plugin to GWT 2.0.2, then I created a web
application without modifying it. I met a problem while wanting to run
the unchanged app locally in development mode : The "development mode"
tab pop up and give me the address to paste in my favorite browser :
http://127.0.0.1:8888/CompaGB.html?gwt.codesvr=127.0.0.1:9997
When I do so I get :
Page load error
Failed to Connect
Firefox can't establish a connection to the server at 127.0.0.1:8888.
I don't know where to start to debug that, can anyone help ?
Gracias
Thomas

PS : When I compile and run in Production Mode I get the "web
application starter projet" page like in the example

[John Denley]

Im not sure what the problem is here, but Ive had the same problem, and all I did was to change the first "127.0.0.1" to "localhost" and it worked OK after that....

In my current development phase I dont have time to mess around trying to fix things properly if I can find a workable workaround, so Im OK with this for now.

I have a slightly different problem in that my application keeps dropping the bit after the portnumber (8888) and then running the previously deployed version, rather than the current development version, which is very irritating!

HTH,
John

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Fabiano]

I have reminds about being something in 2.0.2 changelog about bindings
(in develpement mode). Perhaps you should look to the GWT changelog
too.

[Thomas]

Switching to localhost didn't do the trick for, thanks for the tip
anyway.
I think I should fiddle with my hosted mode execution script or set up
my own server instead of Jetty, when I will have the time...

[Mahmoud Abou-Nassif]

I got the exact same problem with my server! Are you getting a security permission exception as well?
Do you know where the jetty files are located on the system? Maybe you can grant permission by configuring the server?

[Mahmoud Abou-Nassif]

This might help:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/cd39774877d1e320/8924f3f46c95b939?hl=en&pli=1

[Chris Lercher]

You saved my day. I also remembered reading about this option
somewhere, but couldn't find it anymore. The info appears to be only
in the changelog, I don't see it anywhere in the docs.

So, to be able to debug from a browser on a different machine, we must
add "-bindAddress 0.0.0.0" to the arguments of the devmode launch now
(BTW, I think it's good that binding only to 127.0.0.1 is the default
now). With some networking setups, you may have to do that even to
connect to 127.0.0.1. Please be aware, that this allows everyone in
your network to connect to your code server.

[Jim Douglas]

FWIW, it's at the top of the release notes:

http://code.google.com/webtoolkit/release-notes.html#Release_Notes_2_0_1

[Fabiano]

On Feb 17, 6:28 pm, Chris Lercher <cl_for_mail...@gmx.net> wrote:
> You saved my day.

I'm quite a noob, and I'm so happy when I hit the target !
(translated: being useful)
Regards

[Thomas]

-bindAddress 0.0.0.0 worked, thanks for having hit my target ;-)

[Mathieu]

Hi everybody,

How can I set up the bindAdress on eclipse ???

Thanks

[Mathieu]

Ok,

Just had to add the following to Run Config -> Argument and then
Program Arguments "-bindAddress 0.0.0.0"