ICEfaces-EE
  1. ICEfaces-EE
  2. IPCK-27

Superfluous Reload when shutdown node is brought back up again

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.1 Beta
    • Fix Version/s: 1.8.2.GA
    • Component/s: Enterprise Push Server
    • Labels:
      None
    • Environment:
      WebLogic Server 10.3 Cluster, ICEfaces Core, ICEfaces Enterprise Push Server

      Description

      When a shutdown node is brought back up again an additional reload can be experienced by clients on the other node(s) within the cluster.

        Issue Links

          Activity

          Jack Van Ooststroom created issue -
          Ken Fyten made changes -
          Field Original Value New Value
          Fix Version/s 1.8.2 [ 10201 ]
          Assignee Ken Fyten [ ken.fyten ] Deryk Sinotte [ deryk.sinotte ]
          Ken Fyten made changes -
          Fix Version/s 1.8.2.GA_P01 [ 10221 ]
          Fix Version/s 1.8.2.GA [ 10201 ]
          Ken Fyten made changes -
          Fix Version/s 1.8.2.GA [ 10201 ]
          Fix Version/s 1.8.2.GA_P01 [ 10221 ]
          Assignee Deryk Sinotte [ deryk.sinotte ] Jack Van Ooststroom [ jack.van.ooststroom ]
          Jack Van Ooststroom made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Hide
          Jack Van Ooststroom added a comment -

          Fixing the mutating session ID issue, probably fixes this as well.

          Show
          Jack Van Ooststroom added a comment - Fixing the mutating session ID issue, probably fixes this as well.
          Jack Van Ooststroom made changes -
          Link This issue depends on IPCK-46 [ IPCK-46 ]
          Hide
          Jack Van Ooststroom added a comment -

          Fixing the mutating JSESSIONID issue indeed fixes this problem. No excess reload is seen anymore when another node is started back up again in a cluster. Marking this one as FIXED.

          Show
          Jack Van Ooststroom added a comment - Fixing the mutating JSESSIONID issue indeed fixes this problem. No excess reload is seen anymore when another node is started back up again in a cluster. Marking this one as FIXED.
          Jack Van Ooststroom made changes -
          Status In Progress [ 3 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Ken Fyten made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            • Assignee:
              Jack Van Ooststroom
              Reporter:
              Jack Van Ooststroom
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: