I am getting a similar error:
Nov 15, 2009 7:24:24 PM com.google.apphosting.utils.jetty.JettyLogger
info
INFO: jetty-6.1.x
Nov 15, 2009 7:24:25 PM com.google.apphosting.utils.jetty.JettyLogger
info
INFO: Started selectchannelconnec...@0.0.0.0:8080
The server is running at http://localhost:8080/
2009-11-15 14:24:25.396 java[58372:80f] [Java CocoaComponent
compatibility mode]: Enabled
2009-11-15 14:24:25.400 java[58372:80f] [Java CocoaComponent
compatibility mode]: Setting timeout for SWT to 0.100000
Nov 15, 2009 7:24:25 PM
com.google.apphosting.utils.jetty.DevAppEngineWebAppContext
disableTransportGuarantee
INFO: Ignoring <transport-guarantee> for /* as the SDK does not
support HTTPS.  It will still be used when you upload your
application.
Nov 15, 2009 7:24:25 PM
com.google.apphosting.utils.jetty.AppEngineAuthentication
$AppEngineAuthenticator authenticate
INFO: Got /console.html but no one was logged in, redirecting.
Nov 15, 2009 7:24:27 PM com.google.apphosting.utils.jetty.JettyLogger
warn
WARNING: handle failed
java.io.IOException: FULL head
        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:381)
        at org.mortbay.io.nio.SelectChannelEndPoint.run
(SelectChannelEndPoint.java:396)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run
(BoundedThreadPool.java:442)
Nov 15, 2009 7:24:27 PM com.google.apphosting.utils.jetty.JettyLogger
warn
WARNING: handle failed
java.io.IOException: FULL head
        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:381)
        at org.mortbay.io.nio.SelectChannelEndPoint.run
(SelectChannelEndPoint.java:396)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run
(BoundedThreadPool.java:442)

I am running from Eclipse Galileo, on a Mac, GWT 1.7.1, GXT 2.0.1.

Does anyone know the name of the file that is keeping the cookies for
the hosted mode browser?

On Nov 2, 11:45 pm, Rodrigo <rodrigoglsi...@gmail.com> wrote:
> Hi,
>
> Same here.
>
> GXT does use cookies for storing theme related things.
>
> See:http://www.extjs.com/deploy/gxtdocs/com/extjs/gxt/ui/client/state/Sta...
>
> It seems it is writing the cookies many times on the file
> <user>@localhost[1].txt.
>
> After deleting this file my application seems to work. I say "seems"
> because there
> is another error that looks like has nothing to do with the original
> post.
>
> [ERROR] Unable to load module entry point class com.xxx.App (see
> associated exception for details)
> com.google.gwt.core.client.JavaScriptException: (TypeError):
> '$doc.defaultView' is null or not an object
>  number: -2146823281
>  description: '$doc.defaultView' is null or not an object
>         at
> com.extjs.gxt.ui.client.core.impl.ComputedStyleImpl.getComputedStyle
> (Native Method)
>         at
> com.extjs.gxt.ui.client.core.impl.ComputedStyleImpl.getStyleAttribute
> (ComputedStyleImpl.java:27)
>         at com.extjs.gxt.ui.client.core.El.getStyleAttribute(El.java:1236)
>         at com.extjs.gxt.ui.client.util.IconHelper.createStyle
> (IconHelper.java:77)
>         at com.extjs.gxt.ui.client.util.IconHelper.create(IconHelper.java:
> 107)
>         at com.extjs.gxt.ui.client.util.IconHelper.create(IconHelper.java:93)
>         at com.extjs.gxt.ui.client.widget.button.Button.setIconStyle
> (Button.java:357)
>         at com.xxx.App.Editor.<init>(Editor.java:104)
>         at com.xxx.App.onModuleLoad(App.java:27)
>
> R.
>
> On Oct 28, 1:12 pm, Rajeev Dayal <rda...@google.com> wrote:
>
> > Hm, I would have expected that to work. Can you verify that when this
> > problem happens, you have large cookies in the directories that you tried to
> > clear?
>
> > I believe that the Vista cookies directory is:
>
> > C:\Users\ your user name\AppData\Roaming\Microsoft\Windows\Cookies
>
> > 2009/10/17 lain <yana-afanas...@ya.ru>
>
> > > > My suspicion is that there is some sort of cookie problem
> > > You are completely right.
>
> > > Now my application works fine without any configurations (because
> > > cookies expiration date has come, I think), so this bug was really a
> > > problem with cookies.
> > > But this problem may occur again in the future. =(
>
> > > If you know where the hosted browser stores cookies, could you tell
> > > me? Probably, they were not stored in those directories, which I
> > > cleaned.
>
> > > On 14 окт, 21:58, Rajeev Dayal <rda...@google.com> wrote:
> > > > As an FYI, I think the default buffer size on Jetty 6 is 8k, so your
> > > current
> > > > setting will not change anything. However, you should really not need to
> > > > modify Jetty's parameters in this way. Do you have any idea as to why
> > > your
> > > > request header could be more than 8k in size?
> > > > Can you compile your app, and then use FireFox with Firebug, and post
> > > your
> > > > HTTP Request header (maybe attach it as a text file, if it is indeed
> > > 8k+).
> > > > - Показать цитируемый текст -

--

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-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=.


Reply via email to