Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-6529

Investigate having DistributedReplicantManager send all notifications via async thread

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: No Release
    • Component/s: Clustering
    • Labels:
      None
    • Affects:
      Documentation (Ref Guide, User Guide, etc.), Release Notes, Compatibility/Configuration

      Description

      DRM currently dispatches remotely originated notifications to registered ReplicantListeners via its AsynchKeyChangeHandler thread. Notifications originating from local changes to the DRM are dispatched via the calling thread. This can lead to deadlocks a la the attached thread dump.

      Task is to investigate having the locally originating notifications dispatched via the async thread.

      This can be a pretty significant change, as I believe there's a fair bit of code that 1) registers as a DRM listener 2) invokes on the DRM 3) expects a callback from the DRM 4) continues on. Having #3 occur on a different thread could break things. And having the original thread somehow block after #2 until the desired callback comes in would defeat the purpose.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                brian.stansberry Brian Stansberry
                Reporter:
                brian.stansberry Brian Stansberry
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: