ICEfaces
  1. ICEfaces
  2. ICE-4716

Use EnvironmentAdaptingServlet only for the blocking connection

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.8.1
          • Fix Version/s: 1.8.2-RC1, 1.8.2
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            server

            Description

            Currently one object stack, which includes the Thread Blocking environment or ARP (Asynchronous Request Processing) adaptation, is used to handle both blocking and non-blocking requests. As this can cause non-blocking requests to potentially interact with the semaphore logic as well, we should consider introducing an additional object stack in order to separate blocking and non-blocking request handling.

              Activity

              Ascending order - Click to sort in descending order
              Mircea Toma created issue -
              Mircea Toma made changes -
              Field Original Value New Value
              Assignee Mircea Toma [ mircea.toma ]
              Mircea Toma made changes -
              Salesforce Case []
              Fix Version/s 1.8.2 [ 10190 ]
              Mircea Toma made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Mircea Toma made changes -
              Salesforce Case []
              Fix Version/s 2.0 [ 10032 ]
              Jack Van Ooststroom made changes -
              Salesforce Case []
              Description Only the blocking connection should be using EnvironmentAdaptingServlet to avoid unnecessary use of semaphores in case thread blocking strategy/adaptation is used. Currently one object stack, which included the Thread Blocking environment or ARP (Asynchronous Request Processing) adaptation, is used to handle both blocking and non-blocking requests. As this can cause non-blocking requests to potentially interact with the semaphore logic as well, we should consider introducing an additional object stack in order to separate blocking and non-blocking request handling.
              Jack Van Ooststroom made changes -
              Salesforce Case []
              Description Currently one object stack, which included the Thread Blocking environment or ARP (Asynchronous Request Processing) adaptation, is used to handle both blocking and non-blocking requests. As this can cause non-blocking requests to potentially interact with the semaphore logic as well, we should consider introducing an additional object stack in order to separate blocking and non-blocking request handling. Currently one object stack, which includes the Thread Blocking environment or ARP (Asynchronous Request Processing) adaptation, is used to handle both blocking and non-blocking requests. As this can cause non-blocking requests to potentially interact with the semaphore logic as well, we should consider introducing an additional object stack in order to separate blocking and non-blocking request handling.
              Ken Fyten made changes -
              Fix Version/s 1.8.2-RC1 [ 10210 ]
              Fix Version/s 2.0 [ 10032 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]

                People

                • Assignee:
                  Mircea Toma
                  Reporter:
                  Mircea Toma
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: