Thanks for your comments Alexey - explained a great deal.
regards
mark
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839195#3839195
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3839195
I submitted a bug report for this
http://sourceforge.net/tracker/index.php?func=detail&aid=975215&group_id=22866&atid=376685
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839188#3839188
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting
First of all, flushCache() will actually flush the cache.
It will try to passivate the cached instances. Those instances that are in use
(enlisted in transactions) won't be passivated but still will be evicted from the
cache. Nevertheless, the instances remain associated with the transaction and
Would there be any benefit from calling Management Bean method flushCache() on the
entity beans EntityContainer?
We've tried this and it causes the beans to passivate. We could the just truncate the
table as previously suggested.
Any ideas how this flushCache() might sit with any entity beans t
It's fine as long as the fields are "out of date" and not in use by the CMPs anymore.
In our scenario we are deleting records older then
1 week. The table is a cache for temporary mapping and we have tuned the CMP cache to
expire the records if they are 6 days or older, and the nature of the map
Keep in mind that with SQL DELETE you could remove some instances that are enlisted in
current transactions and these transactions will fail to commit.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838737#3838737
Reply to the post :
http://www.jboss.org/ind
We are using the data source and make the bulk delete with a normal query.
/G
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3838715#3838715
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3838715
--
