A customer has reported the following issue:

If I visit a page and sit still long enough without a push update, eventually, a hit to /eps/block/receive-updated-views will result in a 500 error. This generates a JS error as follows:
"NetworkError: 500 Internal Server Error - http://hutch:7092/eps/block/receive-updated-views"

The stack trace in the weblogic log looks like:
####<Oct 20, 2011 10:14:55 PM GMT> <Error> <HTTP> <hutch.networkcar.com> <GAMMA.portal1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319148895057> <BEA-101017> <[ServletContext@2015307879[app:eps module:eps.war path:/eps spec-version:null]] Root cause of ServletException.
java.io.IOException: Response has already been committed for: weblogic.servlet.http.RequestResponseKey@850c241b
       at weblogic.servlet.http.AbstractAsyncServlet.notify(AbstractAsyncServlet.java:128)
       at com.icesoft.faces.push.server.arp.internal.WebLogicAdaptingServlet.doRequest(WebLogicAdaptingServlet.java:117)
       at weblogic.servlet.http.AbstractAsyncServlet.service(AbstractAsyncServlet.java:99)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
       at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
       at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
       at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
       at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183)
       at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3717)
       at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
       at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
       at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
       at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
       at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
       at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
       at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
       at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)


I will upload to the ftp server a war that deploys on 10.3.5 and will reproduce this error consistently. To see the error, visit http://[hostname]/nwf-sample/xhtml/doNothing.seam and wait. A few requests to receive-updated-views will likely complete successfully, but eventually there will be a 500 error.

In contrast, if you visit http://[hostname]/nwf-sample/push-clock the 500 error doesn't occur (the major difference between the two pages being that on push-clock there is a push update every second).

The un/pw for the sample app is icefaces/icefaces.

Please let me know if there's a change that needs to be made to my web.xml, weblogic config, or something else to prevent this error. I'd rather not have my logifles filling up with this stacktrace, but more importantly, I don't want my users' browser to be getting this js error.