See http://jira.jboss.com/jira/browse/JBCACHE-1007 for a JIRA that will break
the reference chain from the Synchronization back to your object.
If JOTM is not fixable, it should be fairly straightforward for you to patch
your JBoss Cache instance.
View the original post :
http://www.jboss.com/
"[EMAIL PROTECTED]" wrote : Does the reference chain from the JOTM object lead
through a javax.transaction.Synchronization implementation? For example,
org.jboss.cache.interceptors.TxInterceptor$RemoteSynchronizationHandler (or
TxInterceptor$LocalSynchronizationHandler)?
|
Yes it does. Just
Does the reference chain from the JOTM object lead through a
javax.transaction.Synchronization implementation? For example,
org.jboss.cache.interceptors.TxInterceptor$RemoteSynchronizationHandler (or
TxInterceptor$LocalSynchronizationHandler)?
If not, please post the full reference chain.
If
I think there should be a way to clear an entire area in the cache (as a bulk).
Finding all the POJOs in the cache and deleting them one by one, sound
expensive.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025003#4025003
Reply to the post :
http://ww
This is a usage problem. PojoCache creates internal nodes in /__JBossInternal__
which aren't cleared since PojoCache is bypassed for the bulk delete operation.
So basically any object that has attach() called on it, can only be removed via
the PojoCache detach method.
Also, the structure __JBos
See http://jira.jboss.com/jira/browse/JBCACHE-990
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024431#4024431
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024431
___
jboss
Thanks for this, will investigate.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024427#4024427
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024427
___
jboss-user mailing l
