Activity

From 10/25/2013 to 11/23/2013

10:45 AM Bug #2204: concurrency issue between user authentication and security cache refresh by the admin...: This is a first pass at the security cache field in SecurityManager:
# always use @getCache@ when accessing it.
# f... Constantin Asofiei

12:48 PM Bug #2204: concurrency issue between user authentication and security cache refresh by the admin...: > Well, this doesn't guarantee that another method call will not access a different generation (i.e. SecurityManager.... Greg Shah
12:17 PM Bug #2204: concurrency issue between user authentication and security cache refresh by the admin...: Greg Shah wrote:
> > During this process, the now-refreshed SecuritManager.cache instance is used to check "are the... Constantin Asofiei
11:11 AM Bug #2204: concurrency issue between user authentication and security cache refresh by the admin...: The design of the SecurityCache provides for "generations" of the cache. Each refresh increments the generation numb... Greg Shah
02:26 AM Bug #2204: concurrency issue between user authentication and security cache refresh by the admin...: There are a few possible solutions for this:
# a short term fix is to not allow authentication if, at the time the S... Constantin Asofiei

02:06 PM Bug #2204: concurrency issue between user authentication and security cache refresh by the admin...: I'm looking for possible NPEs in the code which builds the session report (the SecurityManager.getSessionDescriptor A... Constantin Asofiei
02:05 PM Bug #2204 (WIP): concurrency issue between user authentication and security cache refresh by the...: Constantin Asofiei

05:21 PM Bug #2202: ContextLocal should disallow calls which operate on its data during cleanup(): At least in server mode, @ContextLocal@ should not allow calls to its @get()@ and @set(T)@ methods during cleanup. Th... Eric Faulhaber
04:58 PM Bug #2202 (New): ContextLocal should disallow calls which operate on its data during cleanup(): Eric Faulhaber

Also available in: Atom

FWD » Bugs