[ http://issues.apache.org/jira/browse/JS2-589?page=comments#action_12438611 ] Ethan Adams commented on JS2-589: ---------------------------------
I agree that clearing the ThreadLocal through the pipeline is the best immediate fix. However, I'd hate to see a clear() method as part of the PermissionManager interface. I suppose it could be done by calling implementation specific methods via casting. Again...just my 2 cents. > PermissionManagerImpl use of ThreadLocal for caching causes inconsistent > results > -------------------------------------------------------------------------------- > > Key: JS2-589 > URL: http://issues.apache.org/jira/browse/JS2-589 > Project: Jetspeed 2 > Issue Type: Bug > Components: Security > Affects Versions: 2.1-dev > Environment: java 1.5, oracle, any OS > Reporter: Ethan Adams > Priority: Critical > > PermissionManagerImpl uses ThreadLocal for permission caching. This means > that once the permissions are loaded for one thread (ex. thread 1), they are > there until someone changes the permissions using the PermissionManager (on > that thread). If permissions are edited on another thread (thread 2), thread > 1 never gets updated. So permissions are inconsistent until the portal is > restarted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
