Subject: Grouper Developers Forum
- From: Arnaud Deman <>
- To: Chris Hyzer <>
- Cc: Grouper Dev <>
- Subject: Re: [grouper-dev] Caching questions
- Date: Tue, 04 Aug 2009 10:18:00 +0200
- Organization: GIP RECIA
Thanks for your answer,
Chris Hyzer a écrit :
Unfortunately when you initialize an EhCache controller, it will create allAs far as I understand, there are several EhCache controllers for each session. For instance, in the method AccessResolverFactory.getInstance(...), instances of WheelAccessResolver and CachingAccessResolver are created, both with their controller (and I suppose with a file system access to the configuration file). Do you think it would be possible to use a unique instance of controller and the GrouperSessions' ids as part of the keys ?
caches configured in the config file. And Grouper was designed to have a
cache boundary in a GrouperSession, so with each new GrouperSession created,
there is a new EhCache controller, and all those dozens of caches.
In fact, initially my problem concerned the version 1.2 of Grouper that we are still using here. We use a custom web service to build our initial hierarchy of groups, and this problem caused a memory leak and after a while a crash. I made a temporary fix by making the cache manager static in EhcacheController. It seems to work but as it is in contradiction with the design of Grouper, I wondered if there is a risk that I introduced a bug...
Parc d'activités les Aulnaies
151 rue de la Juine - 45160 OLIVET
Tel : 02 38 42 14 69
- Caching questions, Arnaud Deman, 08/03/2009
Archive powered by MHonArc 2.6.16.