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 On Mar 9, 11:19 am, Ralph <[email protected]> wrote: > 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. > > On Feb 15, 10:29 pm, "[email protected]" <[email protected]> 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 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. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
