[
https://issues.apache.org/jira/browse/WAVE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284508#comment-13284508
]
Paulo Pires commented on WAVE-276:
----------------------------------
Since we've already got jetty-8.1.1, is this still a valid issue?
See
https://svn.apache.org/repos/asf/incubator/wave/trunk/third_party/runtime/jetty/
> Upgrade Jetty jars to newest stable version.
> --------------------------------------------
>
> Key: WAVE-276
> URL: https://issues.apache.org/jira/browse/WAVE-276
> Project: Wave
> Issue Type: Dependency upgrade
> Reporter: Yuri Zelikov
> Priority: Minor
>
> There are certain jetty errors/exceptions in the WIAB server logs - in the
> waveinabox.net logs.
> Like:
> -----------------------------------
> 2011-05-19 05:51:34.121:WARN::Committed before 404 null
> 2011-05-19 05:51:34.122:WARN::/socket.io/xhr-multipart/
> java.lang.IllegalStateException: Committed
> at org.eclipse.jetty.server.Response.resetBuffer(Response.java:1052)
> at org.eclipse.jetty.server.Response.sendError(Response.java:270)
> ---------------------------------------
> 2011-05-19 05:51:07.549:DBUG::RESPONSE
> /socket.io/xhr-polling/dhED5lWgoV-5WVEkDxR_/1305784265575 200
> 2011-05-19 05:51:07.549:DBUG::return with suspended request
> 2011-05-19 05:51:08.258:DBUG::REQUEST /socket.io/xhr-multipart/ on
> org.eclipse.jetty.server.nio.SelectChannelConnector$2@1c442e7
> With this one it seems like it's OJ that it returns with suspended request
> but it seems to do so without a reason, even all users log out from the
> server. According to some posts on internet it can be caused by Jetty bugs.
> --------------------------------------------------------------------------------------------
> It might be that these two are caused by internal Jetty bugs which might be
> fixed in newer releases - at least I found some clues on the internet.
> http://web.archiveorange.com/archive/v/LLXmL6y25yGHr599zB6j
> http://jira.codehaus.org/browse/JETTY-860
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
