ICEfaces
  1. ICEfaces
  2. ICE-1921

Need to clear browser cookie cache when redeploying applications

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Cannot Reproduce
          • Affects Version/s: 1.6
          • Fix Version/s: 1.7Beta1, 1.7
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            win xp
          • Workaround Exists:
            Yes
          • Workaround Description:
            Hide
            It turns out that if you wait long enough, all viewports will eventually fail with "Connection Lost" messages. If this happens, the cookies are cleaned up okay and you can continue to use the application after you redeploy it without having to clear cookies or restart the browser.

            NOTE: In order to avoid this issue, you must allow each viewport in the browser to fail with either a "Session Lost" or "Connection Lost" message before you attempt to reload the application in the browser, or the cookies from the previous session will not be cleared.

            A work-around might be to set the async ping timing (in the web.xml) to something more aggressive (5 secs?) during development so that the connection lost failure occurs much sooner after the web-app is undeployed:

            The following code example defines the time in milliseconds between heartbeat messages. The default value is 20000 (20 seconds), setting it to 5 seconds will make the wait for the failure message more tolerable for some.

            <context-param>
            <param-name>com.icesoft.faces.heartbeatInterval</param-name>
            <param-value>5000</param-value>
            </context-param>
             
            Show
            It turns out that if you wait long enough, all viewports will eventually fail with "Connection Lost" messages. If this happens, the cookies are cleaned up okay and you can continue to use the application after you redeploy it without having to clear cookies or restart the browser. NOTE: In order to avoid this issue, you must allow each viewport in the browser to fail with either a "Session Lost" or "Connection Lost" message before you attempt to reload the application in the browser, or the cookies from the previous session will not be cleared. A work-around might be to set the async ping timing (in the web.xml) to something more aggressive (5 secs?) during development so that the connection lost failure occurs much sooner after the web-app is undeployed: The following code example defines the time in milliseconds between heartbeat messages. The default value is 20000 (20 seconds), setting it to 5 seconds will make the wait for the failure message more tolerable for some. <context-param> <param-name>com.icesoft.faces.heartbeatInterval</param-name> <param-value>5000</param-value> </context-param>  

            Description

            redeploying ICEfaces pps require either restarting the app server or clearing browser cookies. Or else a SessionExpiredException may occur:

             20.07.2007 10:47:46 *ERROR* ([Persistent Faces Servlet]) : Servlet.service() for servlet Persistent Faces Servlet threw exception
            javax.servlet.ServletException: Session expired
            at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:38)
            at com.icesoft.faces.webapp.http.servlet.PathDispatcher$Matcher.serviceOnMatch(PathDispatcher.java:52)
            at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:29)
            at com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:65)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
            at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
            at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
            at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
            at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
            ...

              Activity

              Descending order - Click to sort in ascending order
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]
              Assignee Priority P3
              Assignee Mircea Toma [ mircea.toma ]
              Ken Fyten made changes -
              Fix Version/s 1.7 [ 10080 ]
              Mircea Toma made changes -
              Status Reopened [ 4 ] Resolved [ 5 ]
              Resolution Cannot Reproduce [ 5 ]
              Ken Fyten made changes -
              Fix Version/s 1.7Beta1 [ 10121 ]
              Fix Version/s 1.7 [ 10080 ]
              Ken Fyten made changes -
              Workaround Description The following code example defines the time in milliseconds between heartbeat messages. The default value is 20000 (20 seconds).

              <context-param>
              <param-name>com.icesoft.faces.heartbeatInterval</param-name>
              <param-value>20000</param-value>
              </context-param>
                              		It turns out that if you wait long enough, all viewports will eventually fail with "Connection Lost" messages. If this happens, the cookies are cleaned up okay and you can continue to use the application after you redeploy it without having to clear cookies or restart the browser.

              NOTE: In order to avoid this issue, you must allow each viewport in the browser to fail with either a "Session Lost" or "Connection Lost" message before you attempt to reload the application in the browser, or the cookies from the previous session will not be cleared.

              A work-around might be to set the async ping timing (in the web.xml) to something more aggressive (5 secs?) during development so that the connection lost failure occurs much sooner after the web-app is undeployed:

              The following code example defines the time in milliseconds between heartbeat messages. The default value is 20000 (20 seconds), setting it to 5 seconds will make the wait for the failure message more tolerable for some.

              <context-param>
              <param-name>com.icesoft.faces.heartbeatInterval</param-name>
              <param-value>5000</param-value>
              </context-param>
               
              Ken Fyten made changes -
              Workaround Description The following code example defines the time in milliseconds between heartbeat messages. The default value is 20000 (20 seconds).

              <context-param>
              <param-name>com.icesoft.faces.heartbeatInterval</param-name>
              <param-value>20000</param-value>
              </context-param>
               
              Workaround Exists [Yes]
              Ken Fyten made changes -
              Assignee Priority P3
              Ken Fyten made changes -
              Issue Type Bug [ 1 ] Improvement [ 4 ]
              Fix Version/s 1.7 [ 10080 ]
              Assignee Mircea Toma [ mircea.toma ]
              Ken Fyten made changes -
              Fix Version/s 1.6.1 [ 10070 ]
              Philip Breau made changes -
              Resolution Cannot Reproduce [ 5 ]
              Status Closed [ 6 ] Reopened [ 4 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]
              Assignee Priority P1
              Assignee Mircea Toma [ mircea.toma ]
              Mircea Toma made changes -
              Status Reopened [ 4 ] Resolved [ 5 ]
              Resolution Cannot Reproduce [ 5 ]
              Philip Breau made changes -
              Resolution Cannot Reproduce [ 5 ]
              Status Resolved [ 5 ] Reopened [ 4 ]
              Assignee Philip Breau [ philip.breau ] Mircea Toma [ mircea.toma ]
              Ken Fyten made changes -
              Assignee Mircea Toma [ mircea.toma ] Philip Breau [ philip.breau ]
              Mircea Toma made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Cannot Reproduce [ 5 ]
              Ken Fyten made changes -
              Fix Version/s 1.6.1 [ 10070 ]
              Assignee Priority P1
              Assignee Ken Fyten [ ken.fyten ] Mircea Toma [ mircea.toma ]
              Philip Breau made changes -
              Assignee Ken Fyten [ ken.fyten ]
              Philip Breau made changes -
              Support Customer Ref. #s 713
              Philip Breau made changes -
              Field Original Value New Value
              Summary Need to clear browser cache when redeploying applications Need to clear browser cookie cache when redeploying applications
              Philip Breau created issue -

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Philip Breau
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: