[
https://jira.jboss.org/jira/browse/JBAS-6529?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-6529:
-----------------------------------
Fix Version/s: Backlog
(was: JBossAS-6.0.0.M3)
Affects: [Documentation (Ref Guide, User Guide, etc.),
Compatibility/Configuration, Release Notes] (was: [Release Notes, Documentation (Ref
Guide, User Guide, etc.), Compatibility/Configuration])
Investigate having DistributedReplicantManager send all notifications
via async thread
--------------------------------------------------------------------------------------
Key: JBAS-6529
URL:
https://jira.jboss.org/jira/browse/JBAS-6529
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: Backlog
Attachments: threadDump-1.html
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira