Hosted Browser problem

[Andy]

Hi,

I am encountering a problem trying to create and debug a GWT app. I
have Eclipse 3.4 installed and the Google Plugin for Eclipse which
includes GWT 1.6.4.

I have created a new web application project and have not yet made any
changes to the greeting service sample that was created. When
attempting to debug this project the server and hosted browser window
start up. The hosted browser looks to have the correct URL in the
address bar but displays a completely blank page. It doesn't even
reach the breakpoint that I have put on the first line of the
onModuleLoad method. Clicking the 'Compile/Browse' button opens the
same URL in Chrome which displays the greeting service and works as
expected.

I have added '-logLevel ALL' to the program arguments and found that
an exception is being thrown when opening the page in the hosted
browser. I have included the last few messages that are output to the
server.

[SPAM] fields=Accept: */*
Accept-Language: en-gb,sq;q=0.5
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET
CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.0.04506.30; .NET CLR
3.0.04506.648)
Host: localhost:8080
Connection: Keep-Alive

[SPAM] EXCEPTION
org.mortbay.jetty.HttpException: null
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:276)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380)
at org.mortbay.io.nio.SelectChannelEndPoint.run
(SelectChannelEndPoint.java:395)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run
(QueuedThreadPool.java:488)

[SPAM] BAD

I have run out of ideas now. Any suggestions would be greatly
appreciated.

Thanks.

[Andy]

I don't know if anyone is interested but cookies were to blame. I had
a localhost cookie containing data from other web applications, all
completely unrelated to what I was doing but something in the cookie
was causing an exception in the server when using the hosted browser.
Deleting cookies from IE solved the problem.