Grouper Users - Open Discussion List

[Kumi Hagimoto <>]

Hello,

We're using the default grouper.cache.base.properties  (no
grouper.cache.properties overlay used)  and are seeing some results being
cached.   For example, if the "subjectId" is a member of the
"id_path_to_group", a hasMember WS call
/grouper-ws/servicesRest/json/v2_3_000/groups/id_path_to_group/members/subject
Id
will produce resultCode "IS_MEMBER"

I then remove the subjectId from the group via UI and make the same WS call
immediately.   It still returns "IS_MEMBER" for a while.  (~ 60 seconds...)

I then tried adding the following params to grouper.cache.properties, but it
didn't make any difference.
cache.name.internal_dao_hib3_Hib3MemberDAO_FindBySubject.timeToIdleSeconds = 0
cache.name.internal_dao_hib3_Hib3MemberDAO_FindBySubject.timeToLiveSeconds = 0

What controls caching for this particular method?

Thanks,
Kumi