April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-696) Look into JDBMCacheLoader details and potentially promote as a 'recommended' cache loader?

by Manik Surtani (JIRA)

Look into JDBMCacheLoader details and potentially promote as a 'recommended' cache loader? ------------------------------------------------------------------------------------------ Key: JBCACHE-696 URL: http://jira.jboss.com/jira/browse/JBCACHE-696 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0, 1.3.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-723) Proper collection rollback

by Ben Wang (JIRA)

Proper collection rollback -------------------------- Key: JBCACHE-723 URL: http://jira.jboss.com/jira/browse/JBCACHE-723 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 It is not properly yet via the undointerceptor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1030) CR1 Build failing - aopc now requires concurrent.jar

by Bill Middleton (JIRA)

CR1 Build failing - aopc now requires concurrent.jar ---------------------------------------------------- Key: JBCACHE-1030 URL: http://jira.jboss.com/jira/browse/JBCACHE-1030 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.BETA2 Environment: windows ant 1.6.5 Reporter: Bill Middleton Assigned To: Manik Surtani Fix For: 2.0.0.CR1 The aop.InterceptionMarkers.<init> fails during the build of aopc-pojocache, due to the lack of ConcurrentReaderHashMap (from oswego). Placing a copy of concurrent.jar into $JBOSS_CACHE/lib fixes the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-995) Test failure - org.jboss.cache.multiplexer.BuddyGroupAssignmentTest

by Rajesh Rajasekaran (JIRA)

Test failure - org.jboss.cache.multiplexer.BuddyGroupAssignmentTest ------------------------------------------------------------------- Key: JBCACHE-995 URL: http://jira.jboss.com/jira/browse/JBCACHE-995 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Assigned To: Manik Surtani Fix For: 2.0.0.BETA1 org.jboss.cache.multiplexer.BuddyGroupAssignmentTest fails on the release distribution. To reproduce: run ./build.sh dist. Unzip JBossCache-all-2.0.0.BETA1.zip Run ant one.test -Dtest=org.jboss.cache.multiplexer.BuddyGroupAssignmentTest <testcase classname="org.jboss.cache.multiplexer.BuddyGroupAssignmentTest" name="testRemovalFromCluster2Buddies" time="24.523"> <failure message="10.16.7.254:60612 should be a buddy to 10.16.7.254:60606" type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: 10.16.7.254:60612 should be a buddy to 10.16.7.254:60606 at org.jboss.cache.buddyreplication.BuddyReplicationTestsBase.assertIsBuddy(BuddyReplicationTestsBase.java:285) at org.jboss.cache.buddyreplication.BuddyGroupAssignmentTest.testRemovalFromCluster2Buddies(BuddyGroupAssignmentTest.java:131) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) </failure> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-740) Optimistic Locking Scheme: Occasional IllegalStateExceptions on commit

by Carsten Krebs (JIRA)

Optimistic Locking Scheme: Occasional IllegalStateExceptions on commit ---------------------------------------------------------------------- Key: JBCACHE-740 URL: http://jira.jboss.com/jira/browse/JBCACHE-740 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0 Environment: Linux 2.6.15-26-686 #1 SMP PREEMPT Thu Aug 3 03:13:28 UTC 2006 i686 GNU/Linux java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing) JOTM 2.0.10 JUnit 3.8.1 Reporter: Carsten Krebs Assigned To: Manik Surtani Fix For: 2.0.0 The unit test below reproduces "occasional" IllegalStateExceptions (s.b.) on commiting a transaction. This test tries to modify the same node at the same time by different threads in different transactions using the optimistic locking scheme. java.lang.IllegalStateException: there is already a writer holding the lock: GlobalTransaction:<null>:43 at org.jboss.cache.lock.LockMap.setWriterIfNotNull(LockMap.java:96) at org.jboss.cache.lock.IdentityLock.acquireWriteLock(IdentityLock.java:204) at org.jboss.cache.Node.acquireWriteLock(Node.java:431) at org.jboss.cache.Node.acquire(Node.java:386) at org.jboss.cache.interceptors.OptimisticLockingInterceptor.lockNodes(OptimisticLockingInterceptor.java:149) at org.jboss.cache.interceptors.OptimisticLockingInterceptor.invoke(OptimisticLockingInterceptor.java:76) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.TxInterceptor.runPreparePhase(TxInterceptor.java:804) at org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1069) at org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:75) at org.objectweb.jotm.SubCoordinator.doBeforeCompletion(SubCoordinator.java:1487) at org.objectweb.jotm.SubCoordinator.commit_one_phase(SubCoordinator.java:416) at org.objectweb.jotm.TransactionImpl.commit(TransactionImpl.java:239) at OptimisticLockingTest$Worker.run(OptimisticLockingTest.java:135) The Cache Config: ------------------------- <?xml version="1.0" encoding="UTF-8"?> <server> <mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=TreeCache"> <attribute name="NodeLockingScheme">OPTIMISTIC</attribute> <attribute name="CacheMode">LOCAL</attribute> </mbean> </server> The Unit Test: ------------------- import javax.transaction.Transaction; import javax.transaction.TransactionManager; import junit.framework.TestCase; import org.jboss.cache.CacheException; import org.jboss.cache.PropertyConfigurator; import org.jboss.cache.TransactionManagerLookup; import org.jboss.cache.TreeCache; import org.objectweb.jotm.Current; import EDU.oswego.cs.dl.util.concurrent.CyclicBarrier; /** * OptimisticLockingTest */ public class OptimisticLockingTest extends TestCase { private static final String NODE_PATH = "/path/node"; private static final String KEY = "key"; private static final Current jotm = new Current(); private TreeCache cache; protected void setUp() throws Exception { super.setUp(); cache = new TreeCache(); final PropertyConfigurator config = new PropertyConfigurator(); cache.setTransactionManagerLookup(new TransactionManagerLookup() { public TransactionManager getTransactionManager() throws Exception { return Current.getTransactionManager(); } }); config.configure(cache, this.getClass().getResourceAsStream( "/cache-config.xml")); cache.startService(); } public void testSimultanWrite() throws Exception { for (int i = 2; i < 20; i++) { System.out.println(">> testing simultaneous writes with " + i + " threads..."); testSimultanWrite(i); } } public void testSimultanWrite(final int _numThreads) throws Exception { final CyclicBarrier barrier = new CyclicBarrier(_numThreads); Worker[] workers = new Worker[_numThreads]; for (int i = 0; i < workers.length; i++) { workers[i] = new Worker(); workers[i].barrier = barrier; workers[i].value = "worker" + i; if (i == 0) { workers[i].isMaster = true; } workers[i].start(); } for (int i = 0; i < workers.length; i++) { workers[i].join(); } assertNull(workers[0].exception); for (int i = 0; i < workers.length; i++) { assertNull("rollback failed", workers[i].rollbackException); } for (int i = 1; i < workers.length; i++) { assertNotNull("missing exception", workers[i].exception); assertTrue("exception is not of type CacheException", workers[i].exception.getCause() instanceof CacheException); } assertEquals("worker0", cache.get(NODE_PATH, KEY)); cache.getTransactionManager().begin(); cache.remove(NODE_PATH); cache.getTransactionManager().commit(); } private class Worker extends Thread { private CyclicBarrier barrier; private Exception exception; private Exception rollbackException; private String value; private boolean isMaster; /** * @see java.lang.Thread#run() */ public void run() { final TransactionManager txManager = cache.getTransactionManager(); Transaction tx = null; try { // wait for all threads started barrier.barrier(); if (isMaster) { txManager.begin(); cache.put(NODE_PATH, KEY, value); // lets the other threads start writing barrier.barrier(); // wait for other threads to their modification barrier.barrier(); // commit first tx = txManager.getTransaction(); tx.commit(); // lets the other threads commit barrier.barrier(); } else { // wait for master to start transaction barrier.barrier(); txManager.begin(); cache.put(NODE_PATH, KEY, value); // signal modification barrier.barrier(); // wait for master to commit transaction barrier.barrier(); tx = txManager.getTransaction(); tx.commit(); } } catch (Exception e) { exception = e; try { tx.rollback(); } catch (Exception e1) { rollbackException = e1; } } } } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

3
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-882) Migrating JBC 1.x java serialized data to 2.x VAM format

by Galder Zamarreno (JIRA)

Migrating JBC 1.x java serialized data to 2.x VAM format -------------------------------------------------------- Key: JBCACHE-882 URL: http://jira.jboss.com/jira/browse/JBCACHE-882 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.ALPHA1 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Fix For: 2.0.0.GA Write an FAQ entry in which to explain how to transform data stored in 1.x format into the VAM format. Explanation will focus on: "Write a 'bridge' app, which starts 2 instances of JBC (old and new - can these even run in the same VM together?) and yanks data out of one and into the other?" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-885) Bug when calling putObject() with array as argument

by Bela Ban (JIRA)

Bug when calling putObject() with array as argument --------------------------------------------------- Key: JBCACHE-885 URL: http://jira.jboss.com/jira/browse/JBCACHE-885 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Bela Ban Assigned To: Ben Wang Should at least not lead to an exception, we could for example state that we don't support arrays yet. To reproduce: TreeCacheAop cache; long arr=new long[]{1,2}; cache.putObject("arr", arr); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

3
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-912) Fix tutorial

by Manik Surtani (JIRA)

Fix tutorial ------------ Key: JBCACHE-912 URL: http://jira.jboss.com/jira/browse/JBCACHE-912 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 1.4.1.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

4
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-806) Invalidation causes problems with otimistic data versioning and certain edge cases

by Manik Surtani (JIRA)

Invalidation causes problems with otimistic data versioning and certain edge cases ---------------------------------------------------------------------------------- Key: JBCACHE-806 URL: http://jira.jboss.com/jira/browse/JBCACHE-806 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Replication Affects Versions: 1.4.0.SP1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 Related to JBCACHE-793, but that has more to do with fixing the recommended configurations. >From email conversations: Manik >> At the moment, if I do a put() with V1 into CacheA, this sends an invalidation msg to CacheB. If CacheB has V2 already, the invalidation will fail. What you are saying is, this failure should propagate back to CacheA so the put() with V1 will also fail and this will not exist in CacheA's memory. Am I correct? Max >> It wasn't the scenario I had in mind, but this one is probably also relevant. Manik >> Or is the scenario you're trying to paint more like: V2 put into CacheA. CacheB has V1, gets the invalidation msg, and V1 is evicted. Someone now calls a put() on CacheB with V1, and you are afraid this will be written into the cache? This is true, the invalidation back to CacheA will fail, but CacheB will have stale data in the cache. Max >> This is the scenario I had in mind yes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

2
14
0 / 0

[JBoss JIRA] Created: (JBCACHE-739) Exception in a CacheLoader throws ChainingCacheLoader calling method and prevent the call to the next CacheLoaders

by shimi k (JIRA)

Exception in a CacheLoader throws ChainingCacheLoader calling method and prevent the call to the next CacheLoaders ------------------------------------------------------------------------------------------------------------------- Key: JBCACHE-739 URL: http://jira.jboss.com/jira/browse/JBCACHE-739 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0 Reporter: shimi k Assigned To: Manik Surtani Fix For: 2.0.0 All the delegate methods in ChainingCacheLoader throws Exceptions. Each one of the methods iterates on all the configured Cacheloader. public void put(Fqn name, Map attributes) throws Exception { Iterator i = writeCacheLoaders.iterator(); while (i.hasNext()) { CacheLoader l = (CacheLoader) i.next(); l.put(name, attributes); } } Since the methods throws an Exception, Exception in one of the CacheLoaders will throw the thread out of the method. If the Exception will happen before the last CacheLoader, the ChainingCacheLoader will not call the other CachLoaders. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years

3
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2007