Details
Description
Refreshing the Internet Explorer by clicking the refresh button causes a java.net.SocketException in the console output window of
my server (which is Tomcat 5.5). The same behaviour can be seen when using Tomcat 6.0 or JBoss 4.2.0.
At first I thought this is related to Ajax Push events, but it always happens and only when using Internet Explorer (tested with IE 6.0).
-
Hide
- Test_ConnectionResetByPeer.war
- 4.96 MB
- Michael Thiem
-
- META-INF/MANIFEST.MF 0.0 kB
- WEB-INF/faces-config.xml 0.2 kB
- WEB-INF/html_basic.tld 244 kB
- WEB-INF/jsf_core.tld 25 kB
- WEB-INF/lib/backport-util-concurrent.jar 343 kB
- WEB-INF/lib/commons-beanutils.jar 184 kB
- WEB-INF/lib/commons-collections.jar 558 kB
- WEB-INF/lib/commons-digester.jar 107 kB
- WEB-INF/lib/commons-discovery.jar 70 kB
- WEB-INF/lib/commons-el.jar 110 kB
- WEB-INF/lib/commons-fileupload.jar 52 kB
- WEB-INF/lib/commons-logging.jar 52 kB
- WEB-INF/lib/el-api.jar 24 kB
- WEB-INF/lib/icefaces-comps.jar 622 kB
- WEB-INF/lib/icefaces.jar 687 kB
- WEB-INF/lib/jsf-api.jar 356 kB
- WEB-INF/lib/jsf-impl.jar 778 kB
- WEB-INF/lib/jstl.jar 17 kB
- WEB-INF/lib/standard.jar 343 kB
- WEB-INF/lib/xercesImpl.jar 1.15 MB
- WEB-INF/lib/xml-apis.jar 190 kB
- WEB-INF/web.xml 2 kB
- index.jsp 0.2 kB
- main.jspx 0.5 kB
-
- screenshot-1.jpg
- 615 kB
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
When I test this simple demo application within IE 6 and the latest HEAD version of ICEfaces I still get the 'connection reset by peer' exception.
the exception is thrown when ice-extras.js is being loaded which might cause subsequent errors on some components.
any functional impact of this exception has yet to be approved by further tests. However, the MainServlet should be used for
guarding agains that kind of exception.
I had the same problem with my application after I had upgraded to 1.6. The problem disappeared after explicitly disabling resource compressing in the deployment descriptor.
Thanks, Christian!
I explicitly disabled the resource compression in the web.xml file:
<context-param>
<param-name>com.icesoft.faces.compressResources</param-name>
<param-value>false</param-value>
</context-param>
and it worked.
Catch SocketException (IOException) that might be thrown if the browser closed
the connection before consuming the entire stream.
Applied fix to 1.6 branch.
Can't reproduce this with HEAD. I might have fixed this bug along with
ICE-2025.