Grouper Users - Open Discussion List

[Hans Zandbelt <>]

Hi Chris,

Chris Hyzer wrote, On 3/1/10 7:00 PM:
> Unfortunately yes, it is the expected behavior, though, if you let me know 
> the version of Grouper and more details about the calls you are making, we 
> could discuss clearing relevant caches if group updates occur...  if you 
> are connecting to the same web services server, it will work with your use 
> case.  If you do load balancing, and hit a different server in a cluster, 
> then it wont work until we redo how caching works.

I was just asking because the issue also occurs for _new_ groups (see
original mail). I would expect a cache miss for new groups...

We run grouper 1.5.0; no load-balancing involved.

I have set

  hibernate.cache.use_query_cache = false

in grouper.hibernate.properties and restarted tomcat, but the behaviour
did not change.

I guess the other suggestions regarding ehcache won't help then, right?

Regards,

Hans.

> 
> Thanks!
> Chris
> 
> -----Original Message-----
> From: Hans Zandbelt 
> [mailto:]
>  
> Sent: Monday, March 01, 2010 11:55 AM
> To: Chris Hyzer
> Cc: 
> ;
>  
> 
> Subject: Re: [grouper-users] getGroups caching?
> 
> Hi Chris,
> 
> Chris Hyzer wrote, On 3/1/10 2:57 PM:
>> Not sure if that will work or not, if not, then the cache settings are in 
>> ehcache.xml and grouper.ehcache.xml, might only need to change the 
>> defaults, though might need to tweak others in the file.  If you want, I 
>> can try to reproduce it and see exactly what works.
> 
> We will try tweaking the (3) options that you suggested and report back
> on this list.
> 
> Just to be sure: this is expected behaviour under the current caching
> implementation, right?
> 
> Thanks,
> 
> Hans.
> 
> BTW: we use the Grouper 1.5.0 release
> 
>> Thanks,
>> Chris
>>
>> -----Original Message-----
>> From: Hans Zandbelt 
>> [mailto:]
>>  
>> Sent: Monday, March 01, 2010 4:37 AM
>> To: 
>> 
>> Cc: 
>> 
>> Subject: [grouper-users] getGroups caching?
>>
>> Hi,
>>
>> We currently experience an issue when updating group information:
>>
>> when updating the description of an existing group using groupSave, this
>> call returns OK and shows in the response information that the
>> description was indeed updated to the new value.
>>
>> However, a subsequent call to getGroups still returns the old
>> description for that specific group. Only after some delay (half a
>> minute or so), the getGroups call returns the correct information.
>>
>> (BTW: this issue also shows when creating groups: the description does
>> not even exist at first in the getGroups results, only after some delay)
>>
>> It looks like group information for getGroups is cached, at least for
>> the "description" part; is this assumption true, and if so, can we
>> modify this behaviour?
>>
>> Regards,
>>
>> Hans.
>>
> 
> 


-- 
Hans Zandbelt                    

SURFnet                             http://www.surfnet.nl