2. With useARP=true (default), no push-server, with IE7 this error was seen soon after testing began:

2009-05-19 15:06:15.271::WARN: /auctionMonitor/block/receive-updated-views
java.lang.RuntimeException: no message available
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:173)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:56)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)
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:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:295)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: org.mortbay.jetty.RetryRequest
at org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.suspend(SelectChannelConnector.java:445)
at com.icesoft.faces.webapp.http.servlet.JettyAdaptingServlet$ContinuationRequestResponse.captureContinuation(JettyAdaptingServlet.java:59)
at com.icesoft.faces.webapp.http.servlet.JettyAdaptingServlet.service(JettyAdaptingServlet.java:30)
at com.icesoft.faces.webapp.http.servlet.EnvironmentAdaptingServlet.service(EnvironmentAdaptingServlet.java:63)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:62)
at com.icesoft.faces.webapp.http.servlet.SessionVerifier.service(SessionVerifier.java:22)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:23)
at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:153)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:56)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)
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:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:295)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:204)
... 3 more

3. When tested with the push-server, and useARP=false on IE7 the following errors are seen in the log, although the app. appears to function correctly:

2009-05-19 15:36:09.381::WARN: Nested in javax.servlet.ServletException: org.mortbay.jetty.EofException:
org.mortbay.jetty.EofException
at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:760)
at org.mortbay.jetty.AbstractGenerator$Output.flush(AbstractGenerator.java:565)
at org.mortbay.jetty.HttpConnection$Output.flush(HttpConnection.java:904)
at org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:633)
at org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:586)
at org.icefaces.push.server.UpdatedViewsResponseHandler.respond(UpdatedViewsResponseHandler.java:98)
at com.icesoft.faces.webapp.http.servlet.JettyAdaptingServlet.service(JettyAdaptingServlet.java:26)
at com.icesoft.faces.webapp.http.servlet.EnvironmentAdaptingServlet.service(EnvironmentAdaptingServlet.java:63)
at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:62)
at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:23)
at org.icefaces.push.server.PushServlet.service(PushServlet.java:144)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)
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:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:295)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:373)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361)
at org.mortbay.jetty.nio.SelectChannelConnector$RetryContinuation.run(SelectChannelConnector.java:511)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: java.io.IOException: An existing connection was forcibly closed by the remote host
at sun.nio.ch.SocketDispatcher.writev0(Native Method)
at sun.nio.ch.SocketDispatcher.writev(Unknown Source)
at sun.nio.ch.IOUtil.write(Unknown Source)
at sun.nio.ch.SocketChannelImpl.write0(Unknown Source)
at sun.nio.ch.SocketChannelImpl.write(Unknown Source)
at java.nio.channels.SocketChannel.write(Unknown Source)
at org.mortbay.io.nio.ChannelEndPoint.flush(ChannelEndPoint.java:227)
at org.mortbay.io.nio.SelectChannelEndPoint.flush(SelectChannelEndPoint.java:178)
at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:682)
... 26 more

4. When specifying using useARP=false, with no push-server, on IE7, the test completes successfully. So the issue appears to be related to Jetty Continuations.

I fixed a problem with 'no message' Exception handling introduced in ICE-4261. This seems to have fixed the exceptions and the memory leaks.

QA reports the following on 1.8.1 build 4:

The same warnings appears on the console when running selenium scripts to test Auction Monitor on IE7. The warnings come up each time when a new test case is started. If testing it manually there's no warning at all (tested with push server and useARP=true).

Now that the original fix was checked into the repository and applied, the problem appears to have gone away. Tested on IE7, Safari 3, and FF3 with and without Push Server deployed.

So the issue can easily be replicated in IE without Selenium. Simply hit F5 or reload the page in some way. It would appear that breaking the blocking connection in IE on Jetty results in this warning being logged. Our Selenium test suite issues a fresh request for the Auction Monitor home pages as it switches between tests which is why it shows up there and not typically during manual testing. Reloading in Safari or Firefox does not cause this warning to occur.

It happens with or without the Push Server present:

with Push Server, it logs: WARN: /push-server/block/receive-updated-views: org.mortbay.jetty.EofException
without Push Server, it logs: WARN: /auctionMonitor/block/receive-updated-views: org.mortbay.jetty.EofException

The functionality appears to remain intact as the reload is done.

I checked against 1.8.0 and the same behaviour is there as well. I found a Jetty JIRA that appeared to be related:

http://jira.codehaus.org/browse/JETTY-488

It suggested that this was normal behaviour and previously logged too verbosely. I'm not sure where it's getting logged at the moment (our stuff or Jetty) but it may be safe to ignore. My guess is that it's the Jetty ServletHandler class where I find this code:

else if (th instanceof IOException || th instanceof UnavailableException)

Which matches up nicely with what we are seeing. So I'm marking this as Won't Fix as it appears that the logging is related to a relatively benign behaviour.

Re-opened and resolved as Invalid.