ResultCache values not reflecting LDAP values

[Cantor, Scott]

On 7/9/14, 1:51 PM, "David Bantz" <dabantz at alaska.edu> wrote:
>
>Is is conceivable that the attribute FILTER removes ePA from the cached
>LDAP results because it has not been encoded?  That seems odd, but would
>explain why the next trip through the resolver using the cache, the
>resolver finds 0 values.

No. I don't really understand why your caching is so problematic, but I've
never seen issues with either JDBC or LDAP caching. It's really just not
that invasive because it's all internal to the connectors. You get the
same thing out that was generated initially.

Also, the log messages about value count are from your attribute
definitions, not the connectors. I would be suspicious the attribute
definitions themselves are broken in some way, but I would then probably
go in and add logging to the DataConnectors so that when the cached
results get reused, it dumps them out and I could see exactly what it
passed on.

-- Scott