ICEfaces
  1. ICEfaces
  2. ICE-6838

Messages to different destination servlet context paths can be incorrectly concatenated

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.8.2-EE-GA_P02
          • Fix Version/s: EE-1.8.2.GA_P03
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            ICEfaces, Push Server

            Description

            When using multiple ICEfaces applications and Push Server, messages to be send from Push Server to the ICEfaces applications can be incorrectly concatenated, creating the possibility that app1 can receive a message intended for app2. This is only an issue with messages, namely dispose-views, being send from the Push Server to an ICEfaces application if multiple ICEfaces applications are in play.

              Activity

              Hide
              Permalink
              Jack Van Ooststroom added a comment -

              When using the publish methods to publish a message, messages are first being put in a MessagePipeline. Messages in the same MessagePipeline will be concatenated to form on bigger Message before it's being send out. The MessageServiceClient manages a collection of MessagePipeline, each mapped to an identifying key consisting of the Topic Name and Message Type. When HTTP is used as the underlying transport layer of the MessageServiceClient, the current key is not sufficient enough. Adding the Destination Servlet Context Path to the key ensures that Messages with different Destination Servlet Context Paths cannot be concatenated, which is mandatory for HTTP. JMS doesn't suffer from this. Marking this one as FIXED.

              Show
              Jack Van Ooststroom added a comment - When using the publish methods to publish a message, messages are first being put in a MessagePipeline. Messages in the same MessagePipeline will be concatenated to form on bigger Message before it's being send out. The MessageServiceClient manages a collection of MessagePipeline, each mapped to an identifying key consisting of the Topic Name and Message Type. When HTTP is used as the underlying transport layer of the MessageServiceClient, the current key is not sufficient enough. Adding the Destination Servlet Context Path to the key ensures that Messages with different Destination Servlet Context Paths cannot be concatenated, which is mandatory for HTTP. JMS doesn't suffer from this. Marking this one as FIXED.

                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: