It's not clear how the fix can actually solve the problem even if two JaasSecurityManager can be created for the same SecurityDomain, each with its own TimedCahePolicy object
In order for this exception to occur, there must be some code calling TimedCachePolicy.insert() inbetween outside a synchronized block. Yet JaasSecurityManager.updateCache() seems to be the only caller of that method by searching the codebase, which makes that condition unlikely to occur. Scott, could you comment a bit more on that racing condition identified? Thanks, Sean View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3941143#3941143 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3941143 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
