October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (BPEL-200) Redeployment of a changed PAR (with modified .bpel) requires App Server Restart

by Burr Sutter (JIRA)

Redeployment of a changed PAR (with modified .bpel) requires App Server Restart ------------------------------------------------------------------------------- Key: BPEL-200 URL: http://jira.jboss.com/jira/browse/BPEL-200 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 1 Environment: JBoss 4.0.4.GA with EJB3 using beta JEMS installer Reporter: Burr Sutter Assigned To: Alejandro Guizar Simply modifying the .bpel script, running pack-definition and deploy-definition do not reload/restart the process (even though all process instances have terminated). The only thing I've found that refreshes the BPEL engine properly is to restart the App Server. -- 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

18 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JGRP-281) Investigate whether sent messages need to be buffered in NAKACK

by Bela Ban (JIRA)

Investigate whether sent messages need to be buffered in NAKACK --------------------------------------------------------------- Key: JGRP-281 URL: http://jira.jboss.com/jira/browse/JGRP-281 Project: JGroups Issue Type: Task Affects Versions: 2.3 SP1, 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 NAKACK buffers sent messages in sent-table and received messages in received-table. We might be able to discard sent-table entirely because received-table will contain a message sent by oneself ! Once we have loopback in place by default, we can be sure that any message sent by P will be in P's received-table. -- 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

18 years, 11 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-3658) Remote classloading service - Redesign

by Dimitris Andreadis (JIRA)

Remote classloading service - Redesign -------------------------------------- Key: JBAS-3658 URL: http://jira.jboss.com/jira/browse/JBAS-3658 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Remoting Reporter: Dimitris Andreadis Assigned To: Tom Elrod Fix For: JBossAS-4.0.6.CR1 We need to redesign the remote classloading service such that there is more control at the deployment layer on what is exposed. I will create a forum thread where this can be discussed in more detail. Requirement 1: Provide sensible defaults, which probably means no remote classloading by default Requirement 2: Individual deployments can choose whether remote classloading is enabled and what is available remotely Requirement 3: Allow "aspects" of the deployment to enhance what can be downloaded remotely, e.g. RMI/IIOP generated proxies or AOP remoting proxies Requirement 4: Use the spec defined RMIClassloaderSPI (exposed via an MBean) to make this configurable Requirement 5: Alternate implementations, e.g. exposure of remote classloading via a servlet in Tomcat or a custom resource url that triggers the use of invokers to do remote classloading. -- 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

18 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBCACHE-771) PojoCache to have events reacting to transactional context

by Ben Wang (JIRA)

PojoCache to have events reacting to transactional context ---------------------------------------------------------- Key: JBCACHE-771 URL: http://jira.jboss.com/jira/browse/JBCACHE-771 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.1.0 Currently, the 2.0 POJO based events are not tx aware meaning they can't not react to tx rollback (and therefore not sending the events). If we want to acheieve the tx-based events, we will need to use event interceptor and react to before and afterCompletion, perhaps. -- 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

18 years, 11 months

2
2
0 / 0

[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

18 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-708) EOF exception in TcpCacheLoader

by Manik Surtani (JIRA)

EOF exception in TcpCacheLoader ------------------------------- Key: JBCACHE-708 URL: http://jira.jboss.com/jira/browse/JBCACHE-708 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 Happens when a node in the cluster dies. See last few postings in forum thread for details. -- 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

18 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-710) CacheLoader passivation/activation produces recursive exception when loader.remove fails

by Ben Wang (JIRA)

CacheLoader passivation/activation produces recursive exception when loader.remove fails ---------------------------------------------------------------------------------------- Key: JBCACHE-710 URL: http://jira.jboss.com/jira/browse/JBCACHE-710 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0 Reporter: Ben Wang Assigned To: Manik Surtani Priority: Critical Fix For: 2.0.0 I have encountered this problem during ejb3 sfsb port of JBC1.4. This is what happened: In ActivationInterceptor.java, we have: if (n != null && !n.containsKey(TreeCache.UNINITIALIZED)) { if (n.hasChildren()) { if (allInitialized(n)) { log.debug("children all initialized"); remove(fqn); } } else if (loaderNoChildren(fqn)) { log.debug("no children " + n); remove(fqn); } } } } return retval; } private void remove(Fqn fqn) throws Exception { loader.remove(fqn); cache.notifyNodeActivate(fqn, false); if (cache.getUseInterceptorMbeans()&& statsEnabled) m_activations++; } problem arises when loader.remove(fqn) fails (can be a file lock there, e.g.), then if I have a Cache listener to receive nodeActivate event, and in there, I will have to retrieve the node value, e.g., cache.get(fqn, key) to process some logic, then get(fqn, key) will come back to ActivationInterceptor and attempt another .remove() and therefore the recursion. A proposed fix is we should throw exception when removing the node fails in CacheLoader (I am using FileCacheLoader), e.g., DataNotRemovedException. That way, ActivationInterceptor can catch it here and skip event notification (since it won't be valid anyway). -- 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

18 years, 11 months

4
10
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

18 years, 11 months

2
3
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

18 years, 11 months

3
6
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

18 years, 11 months

2
14
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 October 2006