The problem is that as I have multiple users that connect to the repository at the same time and I have to have a session for each one of them and sometimes the session preforms multiple tasks on the node (ading and removing) so I logout() only when my user disconnects from the system.
If for instance , at every acces to the repository, I do session =jcrStoreService.getSession(user); /* do some stuff here */ session.logout(); and then I try to reconnect with this same user with session =jcrStoreService.getSession(user); I have an error message javax.jcr.RepositoryException: this session has been closed Thomas Mueller-6 wrote: > > Hi, > > Did you open many sessions and not close them? This could be the > reason for the performance problem. > > Thanks, > Thomas > > On Nov 15, 2007 9:58 AM, malsi <[EMAIL PROTECTED]> wrote: >> >> >> I have a which is that from time to time the class >> org.apache.jackrabbit.core.state.CacheManager gets fired and this slows >> performance very much. . I know that CacheManager manages the size of >> the >> caches used in Jackrabbit (which has to be dynamic to increase >> performance >> and memory usage) but is there another way to avoid having this >> CacheManager >> class getting fired all the time i.e (schedule it). >> -- >> View this message in context: >> http://www.nabble.com/CacheManager-slowing-performance-tf4810570.html#a13763908 >> Sent from the Jackrabbit - Users mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/CacheManager-slowing-performance-tf4810570.html#a13765115 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
