ICEfaces
  1. ICEfaces
  2. ICE-1943

MainServlet should guard against SocketException

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.6
    • Fix Version/s: 1.6.2, 1.7DR#1, 1.7
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      any
    • Support Case References:
      #4220

      Description

      No matter which application I use I notice the same behaviour:
      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).

        Activity

        Hide
        Mircea Toma added a comment -

        Can't reproduce this with HEAD. I might have fixed this bug along with ICE-2025.

        Show
        Mircea Toma added a comment - Can't reproduce this with HEAD. I might have fixed this bug along with ICE-2025 .
        Hide
        Michael Thiem added a comment -

        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.

        Show
        Michael Thiem added a comment - 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.
        Hide
        Michael Thiem added a comment -

        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.

        Show
        Michael Thiem added a comment - 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.
        Hide
        Christian Schrade added a comment -

        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.

        Show
        Christian Schrade added a comment - 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.
        Hide
        Michael Thiem added a comment -

        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.

        Show
        Michael Thiem added a comment - 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.
        Hide
        Mircea Toma added a comment -

        Catch SocketException (IOException) that might be thrown if the browser closed
        the connection before consuming the entire stream.

        Show
        Mircea Toma added a comment - Catch SocketException (IOException) that might be thrown if the browser closed the connection before consuming the entire stream.
        Hide
        Mircea Toma added a comment -

        Applied fix to 1.6 branch.

        Show
        Mircea Toma added a comment - Applied fix to 1.6 branch.

          People

          • Assignee:
            Unassigned
            Reporter:
            Michael Thiem
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: