failfastInitiailize and propagateResolutionExceptions still not working
Fixed
Description fields
Basics
Logistics
Basics
Logistics
Description
These settings still don't work correctly, the latter more critically so. LDAP definitely, others may be different.
I think it's to do with caching and/or the setting that keeps connectors in a failed state for a specific time window, but the first time you trigger a failure on an LDAP connector, it seems to be graceful, but subsequent attempts cause a total attribute resolution failure of some kind. So you still end up needing a static failover for resiliency.
The failfast problem is probably specific to LDAP...the pools still have to initialize in order for the connector to, even if failFastInit is false. That may not be fixable, I don't know where that all ended up.
These settings still don't work correctly, the latter more critically so. LDAP definitely, others may be different.
I think it's to do with caching and/or the setting that keeps connectors in a failed state for a specific time window, but the first time you trigger a failure on an LDAP connector, it seems to be graceful, but subsequent attempts cause a total attribute resolution failure of some kind. So you still end up needing a static failover for resiliency.
The failfast problem is probably specific to LDAP...the pools still have to initialize in order for the connector to, even if failFastInit is false. That may not be fixable, I don't know where that all ended up.