July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4382) EnterpriseContext lock counting is not synchronized

by Adrian Brock (JIRA)

EnterpriseContext lock counting is not synchronized --------------------------------------------------- Key: JBAS-4382 URL: http://jira.jboss.com/jira/browse/JBAS-4382 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Reporter: Adrian Brock Assigned To: Scott M Stark Fix For: JBossAS-4.2.0.GA The lock counting in org.jboss.ejb.EnterpriseContext is not synchronized. The lock ivar is not even volatile. This variable needs replacing with synchronized method blocks or an oswego concurrent SynchronizedInt. This bug could either cause passivation to be invoked when it shouldn't or vice versa. Additionally, even with this fix, the usage in StatefulSessionInstanceInterceptor needs replacing with something more atomic! if (!ctx.isLocked()) { //take it! ctx.lock(); } -- 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

17 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1108) Move CacheListeners to their own thread pool

by Jason T. Greene (JIRA)

Move CacheListeners to their own thread pool -------------------------------------------- Key: JBCACHE-1108 URL: http://jira.jboss.com/jira/browse/JBCACHE-1108 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assigned To: Manik Surtani Fix For: 2.0.0.CR3 User CacheListeners should be dispatched in their own thread pool to prevent reentrancy problems and delays on cache operations. Evection listeners should still be executed in the app thread. -Jason -- 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

17 years, 11 months

2
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-991) Non-JTA based mechanism for batching invocations

by Brian Stansberry (JIRA)

Non-JTA based mechanism for batching invocations ------------------------------------------------ Key: JBCACHE-991 URL: http://jira.jboss.com/jira/browse/JBCACHE-991 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Currently JBC uses the lifecycle of a JTA Transaction to scope a series of cache invocations doing things like lock release, replication and cache loader storage as part of the transaction commit. Need a mechanism to do this kind of invocation batching that doesn't depend on JTA. Needed to allow callers that don't wish their work to be associated with an active JTA transaction to still get the batching behavior JBC provides. AS web session replication is an example use case. It uses BatchModeTransactionManger to ensure its activity doesn't impact any ongoing transaction. But BatchModeTransactionManager isn't a good JTA transaction manager even though it implements the JTA interfaces. So using it is problematic; it can easily be misused by those who don't understand it's limitations (e.g. hooking it up to a JTA Datasource.) A couple of possible approaches have been discussed: 1) A new API added to Cache. Methods like startBatch(), commitBatch(), rollbackBatch(), along with some internal mechanism to timeout a batch that's been started but never committed/rolled-back. 2) Abstract away the JTA API such that JBC doesn't use JTA directly, but rather its own interfaces that largely parallel TransactionManager and Transaction. Provide an impl that simply wraps a real JTA TransactionManager. BatchModeTransactionManger would be another impl. API includes a method like 'boolean isJTACompliant()' that things like CacheLoader impls can check at startup to confirm they are working with a compatible impl (e.g. if JBDCCacheLoader is configured to use a JTA Datasource but isJTACompliant() returns false, throw an exception at startup.) Apologies if this is a duplicate issue. Thought there was something like this but couldn't find it. -- 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

17 years, 11 months

3
12
0 / 0

[JBoss JIRA] Created: (JBCACHE-841) Be able to set the internal ordering of child nodes and data keys

by Elias Ross (JIRA)

Be able to set the internal ordering of child nodes and data keys ----------------------------------------------------------------- Key: JBCACHE-841 URL: http://jira.jboss.com/jira/browse/JBCACHE-841 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani I believe that this issue is required to resolve JBCACHE-166 satisfactorily. But it would also be a useful (and easily added) feature for JBossCache 2.0. The attached .java file explains two additional methods to add. The internal implementation would likely need to rely on the JDK1.6 java.util.concurrent.ConcurrentSkipListSet and Map implementations to work without change to other code that rely on iteration to work on concurrently modified sets. As JDK 1.6 is new, this might require use of http://dcl.mathcs.emory.edu/util/backport-util-concurrent/doc/api/ for now, or support from the jbossretro to change these JDK1.6 classes to use the backport for 1.5. -- 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

17 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1141) Redesign evictions for greater flexibility

by Manik Surtani (JIRA)

Redesign evictions for greater flexibility ------------------------------------------ Key: JBCACHE-1141 URL: http://jira.jboss.com/jira/browse/JBCACHE-1141 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eviction Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 3.x -- 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

17 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-941) org.jboss.cache.Caches, which allows for users to access a Cache using various collection interfaces

by Elias Ross (JIRA)

org.jboss.cache.Caches, which allows for users to access a Cache using various collection interfaces ---------------------------------------------------------------------------------------------------- Key: JBCACHE-941 URL: http://jira.jboss.com/jira/browse/JBCACHE-941 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani The java.util.Collections utility class supplies useful methods for dealing with legacy interfaces and wrapping collection classes for concurrency, type safety, read-only, etc. In a simiilar vein, I wrote a "Caches" class that returns java.util.Map instances for a Node, which allow data to be modified through the standard Map interface. This I expect to be extremely useful for allowing uses to integrate their existing application with JBoss Cache, and will eliminate some of the confusion of using a new API and they can use the API they know best. Users also often demand an API which is "generic" so that their code is not tied to a particular vendor. There are basically two methods in Caches, one looks like this: Cache cache = DefaultCacheFactory.getInstance().createCache(); Map m = Caches.asMap(cache); m.put("foo", "bar"); The API and examples explain themselves. "Caches" could also include other useful methods for printing or reporting. Note that this functionality could be considered duplicated from PojoCache...) -- 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

17 years, 11 months

3
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-789) DelegatingCacheLoader that can use a load balanced proxy

by Brian Stansberry (JIRA)

DelegatingCacheLoader that can use a load balanced proxy -------------------------------------------------------- Key: JBCACHE-789 URL: http://jira.jboss.com/jira/browse/JBCACHE-789 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.2.0 Using cache mode LOCAL and a DelegatingCacheLoader (aka a far-cache) has the potential to be a very performant cluster topology. But, the far cache is a single point of failure. Idea here is to develop an HA proxy to a cluster of far-caches; proxy pins to one far-cache, but can fail over to another if the primary target fails. -- 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

17 years, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-1015) Notify user (via callback) if application of (async or sync) replication fails

by Bela Ban (JIRA)

Notify user (via callback) if application of (async or sync) replication fails ------------------------------------------------------------------------------ Key: JBCACHE-1015 URL: http://jira.jboss.com/jira/browse/JBCACHE-1015 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Bela Ban Assigned To: Manik Surtani If a replication cannot be applied (no transactions), then invoke a callback notifying the application, so that some corrective action can be taken -- 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

17 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-877) TreeCache usage should not depend on trove.jar

by Galder Zamarreno (JIRA)

TreeCache usage should not depend on trove.jar ---------------------------------------------- Key: JBCACHE-877 URL: http://jira.jboss.com/jira/browse/JBCACHE-877 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1 Reporter: Galder Zamarreno Assigned To: Manik Surtani Priority: Minor A customer is upgrading from JBC 1.1 to 1.4.0.SP1 and even though it only uses plain TreeCache, it gets a NoClassDefFoundError for trove classes. 2006-11-23 13:19:03,781 ERROR RpcDispatcher exception=java.lang.NoClassDefFoundError: gnu/trove/TObjectHashingStrategy This is a TreeCacheAop/PojoCache dependency and therefore, should be isolated and attempted to be loaded only when PojoCache used. -- 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

17 years, 11 months

7
28
0 / 0

[JBoss JIRA] Created: (JBCACHE-797) Cache to provide a Node implementation that can hide the internal metadata

by Ben Wang (JIRA)

Cache to provide a Node implementation that can hide the internal metadata -------------------------------------------------------------------------- Key: JBCACHE-797 URL: http://jira.jboss.com/jira/browse/JBCACHE-797 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ben Wang Assigned To: Manik Surtani Fix For: 2.1.0 This came up from a Forum thread. Can we offer a second node implementation such that we can deposit the metadata into that node that is hiding away from the user? -- 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

17 years, 11 months

4
4
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 July 2007