shibboleth-dev - Re: FailoverDataConnector bug?
Subject: Shibboleth Developers
List archive
- From: Will Norris <>
- To:
- Subject: Re: FailoverDataConnector bug?
- Date: Wed, 5 Mar 2008 22:48:23 -0800
Should be fixed. Now whenever a connector fails, its failover will be registered in its place and used for the remainder of that resolution. This also works with multiple chained connectors. Given three connectors with the failover chain: DC1 -> DC2 -> DC3. If DC1 and DC2 both fail, DC3 will be used in place of both of them for the remainder of the resolution.
-will
On Mar 4, 2008, at 3:31 PM, Jim Fox wrote:
I'm not able to get the failover data connector to work.
This is what appears to be happening:
(In ShibbolethAttributeResolver.java)
1) The first connector (DB1) is tried. It fails.
2) The failover connector (DB2) is tried. It works
and reports one attribute resolved.
3) Having the resolveDependencies call succeed (about line 315)
we turn around and go back to look up all the values we
just resolved. That, however, is looking for a value
from the primary connector (DB1) which unfortunately
has none. So we get back no values.
That's how it appears anyway.
Jim
- FailoverDataConnector bug?, Jim Fox, 03/04/2008
- Re: FailoverDataConnector bug?, Will Norris, 03/06/2008
Archive powered by MHonArc 2.6.16.