[JBoss JIRA] Created: (JBCLUSTER-237) Improve ClusterChooserInterceptor exception messages
by Brian Stansberry (JIRA)
Improve ClusterChooserInterceptor exception messages
----------------------------------------------------
Key: JBCLUSTER-237
URL: https://jira.jboss.org/jira/browse/JBCLUSTER-237
Project: JBoss Clustering
Issue Type: Task
Security Level: Public (Everyone can see)
Components: HA-Client
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
Fix For: HA-Client 2.0.0.BETA1
Stuff like the following needs improvement:
target = (InvokerLocator) lb.chooseTarget(family.get());
if (target == null)
{
if (lastException != null)
{
throw new RuntimeException("cluster invocation failed, last exception was: ", lastException);
}
else
{
throw new RuntimeException("cluster invocation failed");
}
}
failoverCounter++;
}
// if we get here this means list was exhausted
throw new RuntimeException("Unreachable?: Service unavailable.");
--
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
15 years
[JBoss JIRA] Created: (JBCLUSTER-140) Examine need for a distributed service registry outside the AS
by Brian Stansberry (JIRA)
Examine need for a distributed service registry outside the AS
--------------------------------------------------------------
Key: JBCLUSTER-140
URL: http://jira.jboss.com/jira/browse/JBCLUSTER-140
Project: JBoss Clustering
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: Q3Y6
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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years