Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.9.0
    • Component/s: Web
    • Labels:
      None

      Description

      HTTP sessions use the default logic on Tomcat which causes session state to be held in local memory. If multiple SiteWhere instances are started in a cluster, the HTTP sessions are not shared. Use Spring Session backed by Hazelcast to allow sessions to be shared across the cluster. This also requires updating all Spring artifacts to the latest versions since the Hazelcast support in Spring Session is only in the latest releases.

        Attachments

          Activity

            People

            • Assignee:
              dadams Derek Adams [Administrator]
              Reporter:
              dadams Derek Adams [Administrator]
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: