I forgot to mention that I have only observed this problem if the cache is disabled!
| <!-- JAAS security manager and realm mapping --> | <mbean code="org.jboss.security.plugins.JaasSecurityManagerService" | name="jboss.security:service=JaasSecurityManager"> | <attribute name="SecurityManagerClassName"> | org.jboss.security.plugins.JaasSecurityManager | </attribute> | | <!-- DefaultCacheTimeout: Specifies the default timed cache policy timeout | in seconds. | If you want to disable caching of security credentials, set this to 0 to | force authentication to occur every time. This has no affect if the | AuthenticationCacheJndiName has been changed from the default value. | --> | <attribute name="DefaultCacheTimeout">0</attribute> | <!-- DefaultCacheResolution: Specifies the default timed cache policy | resolution in seconds. This controls the interval at which the cache | current timestamp is updated and should be less than the DefaultCacheTimeout | in order for the timeout to be meaningful. This has no affect if the | AuthenticationCacheJndiName has been changed from the default value. | --> | <attribute name="DefaultCacheResolution">60</attribute> | </mbean> | This seems to be a clash with time4tea theory of a cache problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854665#3854665 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3854665 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
