In looking a bug report on how flushing the entity cache was being prevented by the can passivate state of a bean, I see that the flush basically appears to be a pull the rug out from under the container type of operation. We are just emptying the underlying data store without any regard to what calls may be active with a cache value without acquiring the getCacheLock(). Its also not clear how dumping the cache of EnterpriseContext affects the cmp data cache. Please look into the current flush operation and comment on its validity.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
