Key: COMETD-360
URL: http://bugs.cometd.org/browse/COMETD-360
Project: CometD
Issue Type: Bug
Affects Versions: 2.0.0
Environment: cometd 2.0.0.CR2
Reporter: Edward
Priority: Minor
I am using cometd2 component and is working fine, but when I close the windows of my application, appears this error in the log:
java.lang.RuntimeException: java.net.ProtocolException: EOF after reading only: '0' of: '176' promised bytes, out of which at least: '0' were already buffered
at org.eclipse.jetty.util.ajax.JSON$ReaderSource.getNext(JSON.java:1535)
at org.eclipse.jetty.util.ajax.JSON$ReaderSource.hasNext(JSON.java:1502)
at org.eclipse.jetty.util.ajax.JSON.parse(JSON.java:808)
at org.cometd.server.ServerMessageImpl.parseMessages(ServerMessageImpl.java:596)
at org.cometd.server.transport.HttpTransport.parseMessages(HttpTransport.java:48)
at org.cometd.server.transport.LongPollingTransport.handle(LongPollingTransport.java:169)
at org.cometd.server.CometdServlet.service(CometdServlet.java:211)
at org.cometd.server.CometdServlet.service(CometdServlet.java:171)
Caused By: java.net.ProtocolException: EOF after reading only: '0' of: '176' promised bytes, out of which at least: '0' were already buffered
at weblogic.servlet.internal.PostInputStream.complain(PostInputStream.java:93)
at weblogic.servlet.internal.PostInputStream.read(PostInputStream.java:179)
at weblogic.servlet.internal.ServletInputStreamImpl.read(ServletInputStreamImpl.java:228)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
How can I solve it? is missing some configuration or depends of the server?
Thanks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: http://bugs.cometd.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Simone Bordet resolved COMETD-360.
----------------------------------
Assignee: Simone Bordet
Fix Version/s: 2.4.1
Resolution: Not a Bug
The browser may have sent the headers to the server, but not the body when you closed the window (or you may have a buggy intermediary).
This kind of errors are expected on the server, so it's not really a problem.
If you switch to a more recent version of CometD (2.0.0.RC2 is almost 2 years old now), you can override the method that handles JSON parse exception, and eventually log it at a lower level or suppress its logging.
> EOF reached before promised bytes
> ---------------------------------
>
> Key: COMETD-360
> URL: http://bugs.cometd.org/browse/COMETD-360
> Project: CometD
> Issue Type: Bug
> Affects Versions: 2.0.0
> Environment: cometd 2.0.0.CR2
> Reporter: Edward
> Assignee: Simone Bordet
> Priority: Minor
> Labels: EOF
> Fix For: 2.4.1