[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
12 years, 12 months
[JBoss JIRA] Created: (JGRP-1007) Flush: change signature of JChannel#startFlush to include checked exception
by Vladimir Blagojevic (JIRA)
Flush: change signature of JChannel#startFlush to include checked exception
---------------------------------------------------------------------------
Key: JGRP-1007
URL: https://jira.jboss.org/jira/browse/JGRP-1007
Project: JGroups
Issue Type: Task
Affects Versions: 2.6, 2.8
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 3.0
We have to change signature of startFlush method to include checked exceptions in its signature. We have previously relied on boolean return value of startFlush to get information about success of startFlush method invocation. This approach has been proven to be insufficient, particularly in the light of dealing with [JGRP-985]. We need to discriminate various reasons why startFlush failed, i.e due flush collision, missing response from flush member and so on. Therefore, starting with release 3.0 startFlush method will be void and will throw checked exceptions.
--
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
13 years
[JBoss JIRA] Created: (SECURITY-438) LdapAttributeMappingProvider should check for empty attribute list
by Anil Saldhana (JIRA)
LdapAttributeMappingProvider should check for empty attribute list
------------------------------------------------------------------
Key: SECURITY-438
URL: https://jira.jboss.org/jira/browse/SECURITY-438
Project: JBoss Security and Identity Management
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JBossSX
Affects Versions: JBossSecurity_2.0.4.SP1
Reporter: Anil Saldhana
Assignee: Anil Saldhana
=============
java.lang.NullPointerException
at java.util.StringTokenizer.<init>(StringTokenizer.java:182)
at java.util.StringTokenizer.<init>(StringTokenizer.java:204)
at org.jboss.security.mapping.providers.attribute.LdapAttributeMappingProvider.getNeededAttributes(LdapAttributeMappingProvider.java:336)
at org.jboss.security.mapping.providers.attribute.LdapAttributeMappingProvider.performMapping(LdapAttributeMappingProvider.java:204)
at org.jboss.security.mapping.providers.attribute.LdapAttributeMappingProvider.performMapping(LdapAttributeMappingProvider.java:93)
at org.jboss.security.mapping.MappingContext.performMapping(MappingContext.java:54)
==================
--
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
13 years