Connecting to site 127.0.0.1

[sunn...@gmail.com]

This one has been bugging me for a while now, and I haven't seen
anything around like this one.

I have a Eclipse+Cypal Studio project that has grown to a reasonable
size, and while testing I still use the GWT hosted mode to run. My
machine doesn't have anything else running on port 8888, but
occasionally when I start the project, the hosted browser's status bar
just says "Connecting to site at 127.0.0.1" but nothing happens
(browser window is blank). I'd have to close GWT and restart it for it
to work (sometimes 5 or 6 times before it works).

I have no clue what would be causing this or even where to start to
look to try and fix it.

This project uses Hibernate and GWT-Ext, if that helps at all.

[Lothar Kimmeringer]

sunn...@gmail.com schrieb:

> I have a Eclipse+Cypal Studio project that has grown to a reasonable
> size, and while testing I still use the GWT hosted mode to run. My
> machine doesn't have anything else running on port 8888, but
> occasionally when I start the project, the hosted browser's status bar
> just says "Connecting to site at 127.0.0.1" but nothing happens
> (browser window is blank). I'd have to close GWT and restart it for it
> to work (sometimes 5 or 6 times before it works).

Before starting a new server check the process-list if there isn't
still the old one running (still shutting) down. This can lead to
this kind of effect, because the server-socket is still open but
the subsequent systems (i.e. the request-handling thread and the
servlet) are already down.

If there is an old process still running, kill it using the way
you most prefer on the system you use (e.g. kill -9 PID on Unix-
like systems).

Regards, Lothar

[Zed]

I have the same problem, when using hosted mode - "Connecting to site
127.0.0.1" and nothing happens.
Don't understand the reason, the problem appeared without any visible
trigger and now returns all the time.
It happens also when I run the server first time and after very long
stay periods.
Using gwt 1.5.3
Looking urgently for solution..

[sunn...@gmail.com]

Thanks for the suggestion Lothar, but I see nothing of the kind in my
task manager (Win XP).



On Feb 16, 9:32 pm, Lothar Kimmeringer <j...@kimmeringer.de> wrote:
> sunny...@gmail.com schrieb:

[Roberts M.]

The same problem for me, using GWT 1.5.0. It started approx. week ago
and becomes worse and worse since then.

On Feb 16, 4:29 am, "sunny...@gmail.com" <sunny...@gmail.com> wrote:
> This one has been bugging me for a while now, and I haven't seen
> anything around like this one.
>
> I have a Eclipse+Cypal Studio project that has grown to a reasonable
> size, and while testing I still use the GWT hosted mode to run. My
> machine doesn't have anything else running on port 8888, but
> occasionally when I start the project, the hosted browser's status bar

> just says "Connecting to site at127.0.0.1" but nothing happens

[Ralph]

Having the same problem here. Isn't there a way to improve the script
running the hosted. Like use a different port when 8888 is used, or
close previous instance before opening a new one, or make sure that
the previous run released the port before running a new instance.
Hope someone has a solution.

[Sunny]

I have been using TCPView (http://technet.microsoft.com/en-us/
sysinternals/bb897437.aspx) and found that sometimes after closing a
GWT instance, even though the java process has ended theres still a
port in TIME_WAIT under a system process. All I can do is wait for it
to finish waiting....but maybe this might give someone some hints.

http://www.sunny.id.au/gwt/processes.jpg

[Roberts M.]

One workaround could be to change GWT port on every run, using command
line option "-port 8889" (e.g. making 10 scripts, each with different
port).

[Riyaz Mansoor]

Have had this same issue - working on Netbeans 6.5

Restarting the IDE works but that's tooooo long. I'll check out
Lothars suggestion

[lukehashj]

So I've read about this issue with eclipse and the hosted browser and
I've heard that if you switch focus between the development
environment and the hosted browser a few times it will begin to work
again.

Try to click between eclipse and the hosted browser a bunch and see if
that makes it responsive.

-luke