search

phamtuanchip / gwt-comet

Automatically exported from code.google.com/p/gwt-comet
0 stars 0 forks source link

IE 9 Issues #32

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Running the example chat in Internet Explorer
2.
3.

What is the expected output? What do you see instead?
Messages is the expected output, I am seeing no messages in IE

What version of the product are you using? On what operating system?
version 1.2.3

Please provide any additional information below.
I tried setting up my own example of the chat example provided, was successful 
in Firefox and Chrome but when trying to run it in Internet Explorer I receive 
this message in the browser, I also tested the gwt-comet-examples-1.2.3.war in 
a Jetty instance as well as in Tomcat on a Linux server and all are giving the 
same issue.

error false net.zschech.gwt.comet.client.CometTimeoutException: 
http://127.0.0.1:8888/anothertest/comet timeout has expired after 10000ms

Then on the Console in my GWT project I am seeing first this error as an 
"Uncaught exception escaped" in the "Development Mode" tab in Eclipse

10:23:01.971 [ERROR] [anothertest] Uncaught exception escaped

com.google.gwt.core.client.JavaScriptException: (Error): The data necessary to 
complete this operation is not yet available.

    at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:248)
    at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)
    at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:561)
    at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:269)
    at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)
    at com.google.gwt.core.client.impl.Impl.apply(Impl.java)
    at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213)
    at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
    at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
    at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)
    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:292)
    at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:546)
    at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:363)
    at java.lang.Thread.run(Unknown Source)

and under the "Console" tab in Eclipse I am seeing this

[WARN] cometServlet: Error terminating response
org.mortbay.jetty.EofException
    at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:760)
    at org.mortbay.jetty.AbstractGenerator$Output.flush(AbstractGenerator.java:566)
    at org.mortbay.jetty.HttpConnection$Output.flush(HttpConnection.java:911)
    at net.zschech.gwt.comet.server.deflate.DeflaterOutputStream.flush(DeflaterOutputStream.java:100)
    at net.zschech.gwt.comet.server.impl.CountOutputStream.flush(CountOutputStream.java:64)
    at sun.nio.cs.StreamEncoder.implFlush(Unknown Source)
    at sun.nio.cs.StreamEncoder.flush(Unknown Source)
    at java.io.OutputStreamWriter.flush(Unknown Source)
    at net.zschech.gwt.comet.server.impl.CometServletResponseImpl.flush(CometServletResponseImpl.java:366)
    at net.zschech.gwt.comet.server.impl.CometServletResponseImpl.terminate(CometServletResponseImpl.java:290)
    at net.zschech.gwt.comet.server.impl.CometServletResponseImpl.tryTerminate(CometServletResponseImpl.java:300)
    at net.zschech.gwt.comet.server.impl.CometServletResponseImpl.initiate(CometServletResponseImpl.java:227)
    at net.zschech.gwt.comet.server.CometServlet.doCometImpl(CometServlet.java:137)
    at net.zschech.gwt.comet.server.CometServlet.doGet(CometServlet.java:108)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:729)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.handler.RequestLogHandler.handle(RequestLogHandler.java:49)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:324)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:829)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
    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)
Caused by: java.io.IOException: An existing connection was forcibly closed by 
the remote host
    at sun.nio.ch.SocketDispatcher.write0(Native Method)
    at sun.nio.ch.SocketDispatcher.write(Unknown Source)
    at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source)
    at sun.nio.ch.IOUtil.write(Unknown Source)
    at sun.nio.ch.SocketChannelImpl.write(Unknown Source)
    at org.mortbay.io.nio.ChannelEndPoint.flush(ChannelEndPoint.java:160)
    at org.mortbay.io.nio.SelectChannelEndPoint.flush(SelectChannelEndPoint.java:207)
    at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:693)
    ... 32 more

I have read other issues that were similar to this but I am not seeing the same 
problems on mine as they were so figured would post it as a separate issue

Original issue reported on code.google.com by djor...@t-sciences.com on 15 Mar 2012 at 2:27

GoogleCodeExporter commented 9 years ago 
I'm facing the same problem. But, adding some details to the facts order:

1) In the client, first I receive the "Uncaught exception escaped" ('The data 
necessary to complete this operation is not yet available.').

2) X seconds after, in the client, I receive the "CometTimeoutException" 
('timeout has expired after Xms')

3) Then, in the server, after some time, I receive 
"org.mortbay.jetty.EofException".

The client is leaving by timeout, but the server has received the client 
request!

Original comment by ital...@gmail.com on 15 Apr 2012 at 12:48