January 2009 - jbosscache-issues - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1421) Optimize writes on primitives and Strings to short-circuit if there are no changes

by Manik Surtani (JIRA)

Optimize writes on primitives and Strings to short-circuit if there are no changes ---------------------------------------------------------------------------------- Key: JBCACHE-1421 URL: https://jira.jboss.org/jira/browse/JBCACHE-1421 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 3.1.0 E.g., cache.put(fqn, "key", "Hello"); // tx 1 ... wait ... cache.put(fqn, "key", "Hello"); // tx 2 tx 2 should be able to short-circuit the process if there is no change in the payload. Only makes sense for primitives and Strings though. Even primitive arrays are not worth it since it would involve iterating through the array. -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1462) Capturing statistics and binding to JMX should be controlled by separate config options

by Manik Surtani (JIRA)

Capturing statistics and binding to JMX should be controlled by separate config options --------------------------------------------------------------------------------------- Key: JBCACHE-1462 URL: https://jira.jboss.org/jira/browse/JBCACHE-1462 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX Affects Versions: 3.0.1.GA Reporter: Manik Surtani Assignee: Manik Surtani Priority: Minor Fix For: 3.1.0.GA Comment from a contributor on JBCACHE-1444: " Users should be able to instruct jboss cache to add CacheMgmtInterceptor to interceptor chain without registering it as MBean, because they may want to register all beans themselves. There should be a separate flag to exclude the interceptor from the chain. Currently, the only workaround I found is as follows: Cache cache = factory.createCache(configFileName, true); CacheMgmtInterceptor cmi = new CacheMgmtInterceptor(); cache.addInterceptor(cmi, 0); CacheSPI cachespi = (CacheSPI) cache; cachespi.getComponentRegistry().registerComponent(cmi, cmi.getClass()); But I do not think users should be forced to do such hacks :) " -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1304) OrderedSynchronizationHandler not thread safe

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1304?page=com.atlassian.jira.p... ] Manik Surtani updated JBCACHE-1304: ----------------------------------- Fix Version/s: 1.4.1.SP12 (was: 1.4.X) > OrderedSynchronizationHandler not thread safe > --------------------------------------------- > > Key: JBCACHE-1304 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1304 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 1.4.1.GA, 2.0.0.GA, 2.1.0.CR3, 2.1.0.CR4 > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 2.1.0.GA, 1.4.1.SP12 > > > OrderedSynchronizationHandler uses a static Map to hold instances referenced by a Transaction object, and the factory method on the OSH uses this map to retrieve instances. > 1) This map is unguarded and hence not thread safe. > 2) The map is static, which means it is shared across all cache instances in a given JVM. Not intended to work this way. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1304) OrderedSynchronizationHandler not thread safe

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1304?page=com.atlassian.jira.p... ] Manik Surtani updated JBCACHE-1304: ----------------------------------- Fix Version/s: 1.4.X > OrderedSynchronizationHandler not thread safe > --------------------------------------------- > > Key: JBCACHE-1304 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1304 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 1.4.1.GA, 2.0.0.GA, 2.1.0.CR3, 2.1.0.CR4 > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 2.1.0.GA, 1.4.X > > > OrderedSynchronizationHandler uses a static Map to hold instances referenced by a Transaction object, and the factory method on the OSH uses this map to retrieve instances. > 1) This map is unguarded and hence not thread safe. > 2) The map is static, which means it is shared across all cache instances in a given JVM. Not intended to work this way. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-1304) OrderedSynchronizationHandler not thread safe

by Brian Dueck (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1304?page=com.atlassian.jira.p... ] Brian Dueck resolved JBCACHE-1304. ---------------------------------- Resolution: Done Assignee: Manik Surtani (was: Brian Dueck) > OrderedSynchronizationHandler not thread safe > --------------------------------------------- > > Key: JBCACHE-1304 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1304 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 1.4.1.GA, 2.0.0.GA, 2.1.0.CR3, 2.1.0.CR4 > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 2.1.0.GA > > > OrderedSynchronizationHandler uses a static Map to hold instances referenced by a Transaction object, and the factory method on the OSH uses this map to retrieve instances. > 1) This map is unguarded and hence not thread safe. > 2) The map is static, which means it is shared across all cache instances in a given JVM. Not intended to work this way. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1304) OrderedSynchronizationHandler not thread safe

by Brian Dueck (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1304?page=com.atlassian.jira.p... ] Brian Dueck updated JBCACHE-1304: --------------------------------- Affects Version/s: 1.4.1.GA > OrderedSynchronizationHandler not thread safe > --------------------------------------------- > > Key: JBCACHE-1304 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1304 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 1.4.1.GA, 2.0.0.GA, 2.1.0.CR3, 2.1.0.CR4 > Reporter: Manik Surtani > Assignee: Brian Dueck > Fix For: 2.1.0.GA > > > OrderedSynchronizationHandler uses a static Map to hold instances referenced by a Transaction object, and the factory method on the OSH uses this map to retrieve instances. > 1) This map is unguarded and hence not thread safe. > 2) The map is static, which means it is shared across all cache instances in a given JVM. Not intended to work this way. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-1387) Update and test dependencies in JBossAS profile

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1387?page=com.atlassian.jira.p... ] Brian Stansberry closed JBCACHE-1387. ------------------------------------- Fix Version/s: 3.0.2.GA (was: 3.1.0.GA) Resolution: Done > Update and test dependencies in JBossAS profile > ----------------------------------------------- > > Key: JBCACHE-1387 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1387 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 3.0.2.GA > > > Update the profile to match the latest AS 5 dependencies; run the testsuite with this profile. Preferably set up a hudson job to run the testsuite with the profile. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1267) Revert JBCACHE-1266 fix

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1267?page=com.atlassian.jira.p... ] Brian Stansberry updated JBCACHE-1267: -------------------------------------- Fix Version/s: 3.1.0.GA Schedule so I don't forget about this forever. > Revert JBCACHE-1266 fix > ----------------------- > > Key: JBCACHE-1267 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1267 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > Fix For: 3.1.0.GA > > > The fix for JBCACHE-1266 is a workaround that should be reverted when JBCACHE-1265 is fixed. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-1304) OrderedSynchronizationHandler not thread safe

by Brian Dueck (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1304?page=com.atlassian.jira.p... ] Brian Dueck reopened JBCACHE-1304: ---------------------------------- Assignee: Brian Dueck (was: Manik Surtani) Re-opening this issue in order to fix in 1.4.x codestream. > OrderedSynchronizationHandler not thread safe > --------------------------------------------- > > Key: JBCACHE-1304 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1304 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Affects Versions: 2.0.0.GA, 2.1.0.CR3, 2.1.0.CR4 > Reporter: Manik Surtani > Assignee: Brian Dueck > Fix For: 2.1.0.GA > > > OrderedSynchronizationHandler uses a static Map to hold instances referenced by a Transaction object, and the factory method on the OSH uses this map to retrieve instances. > 1) This map is unguarded and hence not thread safe. > 2) The map is static, which means it is shared across all cache instances in a given JVM. Not intended to work this way. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1467) Incorrect JBoss Microcontainer usage docs

by Brian Stansberry (JIRA)

Incorrect JBoss Microcontainer usage docs ----------------------------------------- Key: JBCACHE-1467 URL: https://jira.jboss.org/jira/browse/JBCACHE-1467 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.1.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.0.2.GA MC usage section in JBC docs is out of date; see forum thread. -- 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

15 years, 11 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosscache-issues January 2009