ICEfaces
  1. ICEfaces
  2. ICE-10971

HTTP Status 500 - Session has expired - if increasing session-timeout to larger values

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: EE-4.0.0.GA, EE-3.3.0.GA_P03, 4.1
    • Component/s: Sample Apps
    • Labels:
      None
    • Environment:
      ICEfaces-4.1.0/ ICEfaces-EE-4.0.0.GA/ ICEfaces-EE-3.3.0.GA_P03
      Server: Tomcat7.0.42
      Browsers: all
    • Assignee Priority:
      P3

      Description

      If the <session-timeout> parameter is increased to '4500', there are no problems in running the sample applications, however increasing this value to a larger number such as '45000' causes an "HTTP error 500 - Session has expired" error displayed in the browser window when trying to access the application. The application cannot be accessed, also when reloading the page.
      The error is not visible in the server terminal window.

      I am wondering if there is a maximum value that can be used for this parameter when running ICEfaces apps?

      This can be reproduced with auction and showcase, and most probably with the other sample apps, if increasing the <session-timeout/> value in the web.xml:
      <session-config>
              <session-timeout>45000</session-timeout>
      </session-config>

        Activity

        Carmen Cristurean created issue -
        Carmen Cristurean made changes -
        Field Original Value New Value
        Attachment http500.png [ 22088 ]
        Carmen Cristurean made changes -
        Description If the <session-timeout> parameter is increased to '4500', there are no problems in running the sample applications, however increasing this value to a larger number such as '45000' causes an "HTTP error 500 - Session has expired" error displayed in the browser window when trying to access the application. The application cannot be accessed, also when reloading the page.
        The error is not visible in the server terminal window.

        I am wondering if there is a maximum value that can be used for this parameter when running ICEfaces apps?

        This can be reproduced with auction and showcase, and most probably with the other sample apps.
        If the <session-timeout> parameter is increased to '4500', there are no problems in running the sample applications, however increasing this value to a larger number such as '45000' causes an "HTTP error 500 - Session has expired" error displayed in the browser window when trying to access the application. The application cannot be accessed, also when reloading the page.
        The error is not visible in the server terminal window.

        I am wondering if there is a maximum value that can be used for this parameter when running ICEfaces apps?

        This can be reproduced with auction and showcase, and most probably with the other sample apps, if increasing the <session-timeout/> value in the web.xml:
        <session-config>
                <session-timeout>45000</session-timeout>
        </session-config>
        Ken Fyten made changes -
        Assignee Mircea Toma [ mircea.toma ]
        Fix Version/s EE-4.1.0.GA [ 12171 ]
        Fix Version/s EE-3.3.0.GA_P04 [ 12270 ]
        Priority Major [ 3 ] Minor [ 4 ]
        Assignee Priority P3 [ 10012 ]
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #48458 Fri Feb 26 10:36:24 MST 2016 ken.fyten Fixed Copyright symbol and year in Readme.html.
        Disabled resource-coalescing in showcase by default due to ICE-10971.
        Files Changed
        Commit graph MODIFY /icefaces4/tags/icefaces-4.1.1/icefaces/samples/showcase/showcase/src/main/webapp/WEB-INF/web.xml
        Commit graph MODIFY /icefaces4/tags/icefaces-4.1.1/icefaces/ReadMe.html
        Hide
        Mircea Toma added a comment -

        Refactored session timeout test in SessionTimeoutMonitor to avoid integer overflow for the 'maxInactiveInterval' value.
        Now the maximum value that can be used in web.xml is 35791394 (= Integer.MAX_VALUE / 60).

        Show
        Mircea Toma added a comment - Refactored session timeout test in SessionTimeoutMonitor to avoid integer overflow for the 'maxInactiveInterval' value. Now the maximum value that can be used in web.xml is 35791394 (= Integer.MAX_VALUE / 60).
        Mircea Toma made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #48466 Mon Feb 29 18:08:32 MST 2016 mircea.toma ICE-10971 Refactored session timeout test to avoid integer overflow for the 'maxInactiveInterval' value.
        Files Changed
        Commit graph MODIFY /icefaces4/trunk/icefaces/core/src/main/java/org/icefaces/impl/application/SessionTimeoutMonitor.java
        Hide
        Liana Munroe added a comment -

        Verified ICEfaces 4 trunk, EE-3.3.0 maintenance branch r48469. Tomcat 8, IE 11, 10 ,9, 8, Chrome 48, FF 43.

        Show
        Liana Munroe added a comment - Verified ICEfaces 4 trunk, EE-3.3.0 maintenance branch r48469. Tomcat 8, IE 11, 10 ,9, 8, Chrome 48, FF 43.
        Ken Fyten made changes -
        Security Private [ 10001 ]
        Ken Fyten made changes -
        Fix Version/s EE-4.1.0.BETA [ 13072 ]
        Ken Fyten made changes -
        Fix Version/s 4.2.BETA [ 13091 ]
        Fix Version/s 4.2 [ 12870 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Mircea Toma
            Reporter:
            Carmen Cristurean
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: