On Tue, Jan 10, 2012 at 5:36 PM, Les Hazlewood <[email protected]> wrote: > As mentioned, the ThreadLocal.remove() call will remove the original > map and cause a new Map to be created as necessary for future > ThreadLocal.get() calls. Do you think this is causing you trouble? > Perhaps we should call ThreadLocal.get().clear() instead?
Often clear() is better than nullifying a map but in this case it shouldn't make a difference, either way the securityManager would be lost. Anyway, it'd be a good idea to put a breakpoint on ThreadLocal.remove() and verify that is what's causing the issue and see what's in the call stack at that moment. Kalle
