November 2011 - jbosscache-issues

[JBoss JIRA] (JBCACHE-1609) LegacyRegionManagerImpl#inactivateRegion locks the parent's entire subtree

by Dennis Reed (Created) (JIRA)

LegacyRegionManagerImpl#inactivateRegion locks the parent's entire subtree -------------------------------------------------------------------------- Key: JBCACHE-1609 URL: https://issues.jboss.org/browse/JBCACHE-1609 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Locking Affects Versions: 3.2.8.GA Reporter: Dennis Reed Assignee: Dennis Reed LegacyRegionManagerImpl#inactivateRegion calls lockManager.lockAll on the parent node, so instead of just locking the parent while the region is inactivated, it locks the parent's entire subtree (the entire cache if the region is a child of the root). In combination with JBCACHE-1608, this causes inactivateRegion to lock the parent's entire subtree and never unlock it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] (JBCACHE-1607) LegacyRegionManagerImpl releases locks from other threads

by Dennis Reed (Created) (JIRA)

LegacyRegionManagerImpl releases locks from other threads --------------------------------------------------------- Key: JBCACHE-1607 URL: https://issues.jboss.org/browse/JBCACHE-1607 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Locking Affects Versions: 3.2.8.GA Reporter: Dennis Reed Assignee: Dennis Reed LegacyRegionManagerImpl calls lockManager.unlockAll(NodeSPI) instead of lockManager.unlockAll(NodeSPI, Owner owner). This will cause it to remove any locks currently held by other threads. Due to JBCACHE- lockManager.unlockAll(NodeSPI) is broken, so the effects are limited to the specific node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1604) NullPointerException in ResourceDMBean.invoke()

by Takayoshi Kimura (JIRA)

NullPointerException in ResourceDMBean.invoke() ----------------------------------------------- Key: JBCACHE-1604 URL: https://issues.jboss.org/browse/JBCACHE-1604 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: 3.2.7.GA Reporter: Takayoshi Kimura Assignee: Manik Surtani Priority: Minor ResourceDMBean.invoke(String name, Object[] args, String[] sig) throws NullPointerException when sig == null. JMX spec doesn't guarantee it's non-null, so we should check it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1523) JBoss Cache MBean print* operations return Object's toString()

by Ondrej Žižka (JIRA)

JBoss Cache MBean print* operations return Object's toString() -------------------------------------------------------------- Key: JBCACHE-1523 URL: https://jira.jboss.org/jira/browse/JBCACHE-1523 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ondrej Žižka Assignee: Manik Surtani Priority: Minor 1) Run EAP 5, all config 2) Go to JMX console, jboss.cache:config=ha-partition,service=Cache 3) Invoke print* operations. Cache details: "/ null", as HTML /  null<br/> "Print configuration" returns only java.lang.Object's toString(), e.g. org.jboss.cache.config.Configuration@af91c6fa etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
4
0 / 0

[JBoss JIRA] (JBCACHE-1605) Concurrency issues with multiple threads calling cache.start

by Dennis Reed (Created) (JIRA)

Concurrency issues with multiple threads calling cache.start ------------------------------------------------------------ Key: JBCACHE-1605 URL: https://issues.jboss.org/browse/JBCACHE-1605 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.2.8.GA Reporter: Dennis Reed Assignee: Dennis Reed There is no synchronization on cache.start, and concurrent calls to start the same cache cause errors. This is particularly an issue in AS 5, where caches are retrieved from the EAP CacheManager and the first user of the cache must start it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1410) Cache loaders that use StripedLock do not adequately lock root node when the root node is first added.

by Manik Surtani (JIRA)

Cache loaders that use StripedLock do not adequately lock root node when the root node is first added. ------------------------------------------------------------------------------------------------------ Key: JBCACHE-1410 URL: https://jira.jboss.org/jira/browse/JBCACHE-1410 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 2.0.0.GA Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 3.0.0.GA, 2.X See detail on the forum post. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
12
0 / 0

[JBoss JIRA] (JBCACHE-1606) TimeoutException causes unreleased locks

by Jean-Pierre GRILLON (Created) (JIRA)

TimeoutException causes unreleased locks ---------------------------------------- Key: JBCACHE-1606 URL: https://issues.jboss.org/browse/JBCACHE-1606 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Locking Affects Versions: 1.4.1.SP13 Reporter: Jean-Pierre GRILLON Assignee: Manik Surtani 5 nodes in JBoss Cache, pessimistic locking: /a/b/c1 /a/b/c2 /a/b/locked /a/b/c3 /a/b/c4 And the node "/a/b/locked" is write-locked by another thread. Then try to delete entire node "/a/b". Node.acquireAll successfully acquires write-lock on "/a/b/c1" and "/a/b/c2", but a TimeoutException occurs on "/a/b/locked" (which is expected). After this exception, locks on "/a/b/c1" and "/a/b/c2" are not released. Actually, Node.acquireAll shall return acquired locks, but in this case doesn't return anything but throws an exception. So, previously acquired locks are not in "cache.getLockTable()", and can't be released by UnlockInterceptor. TestCase attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
4
0 / 0

[JBoss JIRA] (JBCACHE-1608) IdentityLock#releaseAll() is not recursive

by Dennis Reed (Created) (JIRA)

IdentityLock#releaseAll() is not recursive ------------------------------------------ Key: JBCACHE-1608 URL: https://issues.jboss.org/browse/JBCACHE-1608 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Locking Affects Versions: 3.2.8.GA Reporter: Dennis Reed Assignee: Dennis Reed Priority: Minor IdentityLock#releaseAll(Object owner) is recursive. IdentityLock#releaseAll() is not recursive. The only caller of these, NodeBasedLockManager expects these to be the same (recursive) except for the owner argument. The result is that NodeBasedLockManager#unlockAll(NodeSPI) does not function correctly (recursively). The similar NodeBasedLockManager#unlockAll(NodeSPI, Object owner) does work correctly. The only caller of NodeBasedLockManager#unlockAll(NodeSPI) is LegacyRegionManagerImpl#inactivateRegion. It appears it should be using NodeBasedLockManager#unlockAll(NodeSPI, Object owner) instead (see JBCACHE-1607). Since this is the only caller of this method, this bug is considered minor. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosscache-issues November 2011