Uploaded image for project: 'ZK'
  1. ZK
  2. ZK-746

session-timeout setting results different timeouts in different application servers

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: 5.0.6
    • Fix Version/s: None
    • Component/s: Configuration
    • Environment:

      Tomcat on windows
      WebSphere cluster and WebLogic cluster on Linux

      Description

      We are using the combination of session-timeout and timer-keep-alive settings to time out a session as soon as the browser is closed.

      In zk.xml, we set the session timeout to 20 seconds:
      <session-config>
      <session-timeout>20</session-timeout>

      It means, we expect the session to be timed out after ~20 seconds, when the browser window is closed.

      During our tests we got different results on different platforms:

      • Tomcat: after 1 minute
      • WebSphere cluster: after 2 minutes
      • WebLogic cluster: after 45 seconds

      We are now wondering how to interpret this result and why such differences exist. Do you have an idea?

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            ozkucur ozkucur
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: