grouper-users - Re: [grouper-users] WebService cache - hasMember

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] WebService cache - hasMember

From: "Hagimoto, Kumi" <>
To: "" <>
Subject: Re: [grouper-users] WebService cache - hasMember
Date: Tue, 11 Jul 2017 22:12:33 +0000
Accept-language: en-US
Authentication-results: internet2.edu; dkim=none (message not signed) header.d=none;internet2.edu; dmarc=none action=none header.from=oregonstate.edu;
Ironport-phdr: 9a23:a6utFxLhS9ybITu/AtmcpTZWNBhigK39O0sv0rFitYgUK/3xwZ3uMQTl6Ol3ixeRBMOAtKIC1rKempujcFJDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBWB6kG1uHQdABLiLQdvY/nuF5TJp8Wxy+2o/ZDPOUNFiCf3Ked9NhKrtQjL89QNjJF5Aqc31hbTpHZUIaJbyX4+dnyJmBOprOe5859m9DhX/7oC6stBG+2uXLk9TPp4BTsnNmcp4+XsrxTMSg2U+nIAXyMbngceUFuN1w3zQpqk6niyjeF6wiTPZcA=
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:99

Hi - just checking to see if anyone has been able to control caching for ws calls.

Thanks,

Kumi

On Jun 28, 2017, at 3:56 PM, Kumi Hagimoto <> wrote:

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

Re: [grouper-users] WebService cache - hasMember, Hagimoto, Kumi, 07/11/2017

List archive

Re: [grouper-users] WebService cache - hasMember