Scott, Given that TimedCachePolicy is created thread-safe, the code try to insert into it are wrapped in synchronized block and it is always try to remove existing entry with same principal before insertion, but we still got IllegalStateException for "Attempt to insert duplicate entry", there must be other thing sneaked behind and changed the cache with principal of same name. Could you help identify what it could be?
So far, it happened only under scenario of different data sources reside on physically different servers, using the same set of encrypted username/password. But the severity of this problem is escalated, since we suspect it might actually cause JDBC connection leak. Thanks for your help. -Wei View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938446#3938446 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3938446 ------------------------------------------------------- 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
