[jboss-jira] [JBoss JIRA] Assigned: (JBCLUSTER-140) Examine need for a distributed service registry outside the AS

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/JBCLUSTER-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry reassigned JBCLUSTER-140:
------------------------------------------

    Assignee:     (was: Brian Stansberry)


> Examine need for a distributed service registry outside the AS
> --------------------------------------------------------------
>
>                 Key: JBCLUSTER-140
>                 URL: https://issues.jboss.org/browse/JBCLUSTER-140
>             Project: JBoss Clustering
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>             Fix For: Backlog
>
>
> Is something like DRM needed outside the AS?  If it is, do we want to use the JBoss Cache based version (creates JBC dependency.)
> DRM is used in two ways:
> 1) To maintain a distributed registry of remote invocation targets.
> 2) To maintain a distributed registry of services, which is done by having the service register a meaningless token under its key rather than a target.  This is used by HASingleton.
> Need to examine whether this kind of thing is needed by Messaging, or whether simple listening for view changes is sufficient.  Listening for view changes could be sufficient if each group member knew how to create a Remoting InvokerLocator for the other members based on the JGroups Address.  But, this presupposes use of consistent ports across the cluster, and that the IP address used by JGroups is the one that Messaging traffic should use.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira