Hi - sorry, have been out of the loop in this for a while - do you still see
this problem?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025021#4025021
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025021
Have you got a unit test that recreates this? One that works on the cache
directly, rather than the MBean?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025054#4025054
Reply to the post :
Add this method to org.jboss.cache.transaction.TransactionTest from cache
1.4.1.SP2 src dist. It causes endless loop
public void testEndlessLoop() {
| try {
| Fqn root = new Fqn();
| Fqn fqn = new Fqn(root, 1L);
|
Thanks for this. Interestingly, this only happens when you try and remove the
root node. Try changing it such that:
| Fqn root = Fqn.fromString(/my/SubRoot);
|
and it works fine.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025106#4025106
Reply
See JBCACHE-999 - your bug got the lucky 999!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025160#4025160
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025160
___
jboss-user
anonymous wrote : See JBCACHE-999 - your bug got the lucky 999!
:-)
Thanks for quick response.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4025309#4025309
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4025309
Upgrade to 1.4.1.SP1 doesnt help. Does anyone has idea where could be problem ?
I can't belive that production version has so serious bug.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4013524#4013524
Reply to the post :
Thanks for spotting this. Yes, this is related to JBCACHE-871, because since
fixing that, nodes aren't removed immediately but are marked as removed instead
and are only cleaned up during tx commit.
The bug is the result of a parent being removed in the same tx as a child is
being implicitly
Thanks for reply. Are you sure that this happen only when deleteting and adding
is in the same tx? My application listenens on the socket, server gets first
request that deletes root node (whith stateless ejb) then after a while I make
another socket request which put new node to cache and
This shld only be within the same tx. The whole concept of marking nodes for
removal does not exist if no txs are used.
If things happen in different txs, e.g., remove in tx 1, and put in tx 2, the
looping in tx 2 is *supposed* to happen until tx 1 commits and finishes the
remove operation
This how I am getting the Loop. I delete root node:
| 15:24:25,709 DEBUG [TxInterceptor] local transaction exists - registering
global tx if not present for Thread[pool-1-thread-3,5,jboss]
| 15:24:25,715 DEBUG [TxInterceptor] local transaction exists - registering
global tx if not present
Do both the txs start on the same cache instance? Or are they n different
instances in the cluster?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4013763#4013763
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4013763
This is the same cache instance. I have edited hostname only in part of log -
sorry.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4013823#4013823
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4013823
13 matches
Mail list logo
