I'd think bypassing the cache would be a bad thing in the future. You might want to look at the 'refresh' method on the PSMLManager service interface:
http://portals.apache.org/jetspeed-1/apidocs/org/apache/jetspeed/services/psmlmanager/PsmlManagerService.html#refresh(org.apache.jetspeed.om.profile.ProfileLocator) I'd dig into that class to gain a better understanding of how caching of psml documents actually happens. What you're experiencing implies that it happens on a user by user basis, which does not make a whole lot of sense to me, at least for group and role based psml documents. Dan --- [EMAIL PROTECTED] wrote: > After a little more research, we discovered one more way to get > around this > issue. There is a setting in JetspeedResource.properties file, > services.PsmlManager.cacheSize. It is default to 100, meaning maximum > 100 > psml pages will be cached. We change that to 0 and it fixed this psml > reference refresh issue. > Is this change recommended? It is obviously for a performance reason > (probably save time on File I/O). With only limited users(<500)using > the > site now, we didn't notice a obvious impact. However, we will have > more > users in the future and the psml cache will be a good thing to have. > Without > turning it off, is there a setting to control the expiration of the > psml > cache? > Andy > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 17, 2004 11:05 AM > To: [EMAIL PROTECTED] > Subject: Refreshing a psml reference > > > We just implemented a Jetspeed 1.5 portal site with tomcat 4.1.18. > The psml > reference is used so that different users can share a group or role > psml > file. When we make a change to the group psml (e.g. adding a portlet > to the > page), the users who have previously login to the site won't see the > change > if they login again (even after a while). However, if the user login > as the > first time, they could see the change. Of course, the change will be > visible > to everyone after bouncing the tomcat. The sequence is like this. > -login as user1 then logout > -change the group psml that is referenced by user1's psml > -login as user2 to verify the referenced psml is changed. > -if yes from pervious step, login as user1 > -too bad, the user1 still don't see the change. > It seems that there is caching happened for user1. However we are not > sure > which setting could affect this. We also waited overnight expecting > the > cache will expire. That did not happen either. > Has anyone actively using reference? Any experience with this issue? > Thanks! > Andy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
