ICEfaces
  1. ICEfaces
  2. ICE-5533

Portal code doesn't set maxInactiveTimeout correctly in WebSphere portal environment

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.8.2-EE-GA
    • Fix Version/s: None
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      WebSphere Portal 6.1.0.1 plus ICEFaces

      Description

      On attempting to create a WebSphere portal environment to test compatibility, the test application was showing session expired immediately on showing up with a second user. It turns out that the maxInactiveTimeout value starts coming back as -1 at some point which throws a wrench into a little calculation http://jira.icefaces.org/browse/ICE-2519 which was setting the timeout to a value causing the application to expire immediately.

      I'm still not sure why the appearance of a second user affects the returned value.

        Activity

        Greg Dick created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Greg Dick
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: