October 2008 - jbosscache-issues - Jboss List Archives

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

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-797?page=com.atlassian.jira.pl... ] Manik Surtani updated JBCACHE-797: ---------------------------------- Fix Version/s: (was: 3.0.0.GA) > Cache to provide a Node implementation that can hide the internal metadata > -------------------------------------------------------------------------- > > Key: JBCACHE-797 > URL: https://jira.jboss.org/jira/browse/JBCACHE-797 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assignee: Manik Surtani > > 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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-55) Make eviction policy compliant with non-string type fqn

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-55?page=com.atlassian.jira.plu... ] Manik Surtani resolved JBCACHE-55. ---------------------------------- Fix Version/s: (was: 3.0.0.GA) Resolution: Won't Fix > Make eviction policy compliant with non-string type fqn > ------------------------------------------------------- > > Key: JBCACHE-55 > URL: https://jira.jboss.org/jira/browse/JBCACHE-55 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2.1 > Reporter: Ben Wang > Assignee: Manik Surtani > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently, if you use eviction policy, then fqn is required to be String type only. To make this compliant, we will depend on dynamic eviction region created programatically. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-55) Make eviction policy compliant with non-string type fqn

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-55?page=com.atlassian.jira.plu... ] Manik Surtani reopened JBCACHE-55: ---------------------------------- Assignee: Manik Surtani (was: Ben Wang) > Make eviction policy compliant with non-string type fqn > ------------------------------------------------------- > > Key: JBCACHE-55 > URL: https://jira.jboss.org/jira/browse/JBCACHE-55 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2.1 > Reporter: Ben Wang > Assignee: Manik Surtani > Original Estimate: 4 days > Remaining Estimate: 4 days > > Currently, if you use eviction policy, then fqn is required to be String type only. To make this compliant, we will depend on dynamic eviction region created programatically. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBCACHE-48) TreeCacheListener that ships data with notification

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-48?page=com.atlassian.jira.plu... ] Manik Surtani reopened JBCACHE-48: ---------------------------------- Assignee: Manik Surtani (was: Bela Ban) > TreeCacheListener that ships data with notification > --------------------------------------------------- > > Key: JBCACHE-48 > URL: https://jira.jboss.org/jira/browse/JBCACHE-48 > Project: JBoss Cache > Issue Type: Feature Request > Affects Versions: 1.2 > Reporter: Bela Ban > Assignee: Manik Surtani > Original Estimate: 2 days > Remaining Estimate: 2 days > > Data are locked, callback carries *ref*, not *value* -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1380) Add UML output to javadocs

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1380?page=com.atlassian.jira.p... ] Manik Surtani updated JBCACHE-1380: ----------------------------------- Fix Version/s: 3.1.0 (was: 3.0.0.GA) > Add UML output to javadocs > -------------------------- > > Key: JBCACHE-1380 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1380 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scripts and processes > Reporter: Manik Surtani > Assignee: Manik Surtani > Priority: Minor > Fix For: 3.1.0 > > > Either yDocs - for which we have an OSS license - or Trustin's APIViz. > http://code.google.com/p/apiviz/ > Pros and cons are that APIViz is F/OSS but requires that you have graphviz installed on the build system. yDocs needs a license and even though we have an OSS license for it, we can't package or distribute it. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-1391) update documentation and FAQs

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1391?page=com.atlassian.jira.p... ] Manik Surtani resolved JBCACHE-1391. ------------------------------------ Resolution: Done > update documentation and FAQs > ----------------------------- > > Key: JBCACHE-1391 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1391 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mircea Markus > Assignee: Manik Surtani > Fix For: 3.0.0.GA > > > Following should be updated in documentation: > 1) document how the configuration will still accept old <mbean ... /> tags, but this is deprecated > 2) document how the <mbean ... /> tag can cause problems with AS 5 (unintentional deployment), and how this can be done properly with the MC using the new <jbosscache ... /> tag > Notes: > Currently the XMLConfigurationParser looks for a <mbean ../> element, under which it pulls out more specific JBoss Cache elements. > This could easily change so the parser to accept this, or on failing to do so, to pick up a <jbosscache ... /> container element. And log a deprecation warning when using the old <mbean ... /> container tag. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1430) JDBCCacheLoader fails to restart connection to DB

by Alexis Yerenkow (JIRA)

JDBCCacheLoader fails to restart connection to DB ------------------------------------------------- Key: JBCACHE-1430 URL: https://jira.jboss.org/jira/browse/JBCACHE-1430 Project: JBoss Cache Issue Type: Quality Risk Security Level: Public (Everyone can see) Components: Cache loaders, Transactions Affects Versions: 2.2.0.GA, 2.2.1.CR2 Environment: Jboss 4.2.2, FreeBSD 6.3, diablo-jdk 1.6, PostgreSQL 8.3.3 on other server, FreeBSD 7.0 Reporter: Alexis Yerenkow Assignee: Manik Surtani Start ear in Jboss with JDBCCacheLoader, restart DB (or wait until network fail and repairs) and look in log for many falling messages like this: 12:52:49,349 ERROR [STDERR] org.jboss.cache.CacheException: Invalid transaction TransactionImple < ac, BasicAction: 7f000001:e318:48fef5cb:37f status: ActionStatus.ABORT_ONLY >, status = 1 12:52:49,349 ERROR [STDERR] at org.jboss.cache.transaction.TransactionTable.assertTransactionValid(TransactionTable.java:367) 12:52:49,350 ERROR [STDERR] at org.jboss.cache.lock.PessimisticNodeBasedLockManager.lock(PessimisticNodeBasedLockManager.java:104) 12:52:49,350 ERROR [STDERR] at org.jboss.cache.lock.PessimisticNodeBasedLockManager.lockPessimistically(PessimisticNodeBasedLockManager.java:76) 12:52:49,350 ERROR [STDERR] at org.jboss.cache.interceptors.PessimisticLockInterceptor.handleGetNodeCommand(PessimisticLockInterceptor.java:316) 12:52:49,351 ERROR [STDERR] at org.jboss.cache.interceptors.base.PostProcessingCommandInterceptor.visitGetNodeCommand(PostProcessingCommandInterceptor.java:257) 12:52:49,351 ERROR [STDERR] at org.jboss.cache.commands.read.GetNodeCommand.acceptVisitor(GetNodeCommand.java:42) 12:52:49,351 ERROR [STDERR] at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:142) 12:52:49,351 ERROR [STDERR] at org.jboss.cache.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:157) 12:52:49,352 ERROR [STDERR] at org.jboss.cache.commands.AbstractVisitor.visitGetNodeCommand(AbstractVisitor.java:94) 12:52:49,352 ERROR [STDERR] at org.jboss.cache.commands.read.GetNodeCommand.acceptVisitor(GetNodeCommand.java:42) 12:52:49,353 ERROR [STDERR] at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:142) 12:52:49,353 ERROR [STDERR] at org.jboss.cache.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:157) 12:52:49,353 ERROR [STDERR] at org.jboss.cache.commands.AbstractVisitor.visitGetNodeCommand(AbstractVisitor.java:94) 12:52:49,353 ERROR [STDERR] at org.jboss.cache.commands.read.GetNodeCommand.acceptVisitor(GetNodeCommand.java:42) 12:52:49,354 ERROR [STDERR] at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:142) 12:52:49,354 ERROR [STDERR] at org.jboss.cache.interceptors.TxInterceptor.attachGtxAndPassUpChain(TxInterceptor.java:266) 12:52:49,354 ERROR [STDERR] at org.jboss.cache.interceptors.TxInterceptor.handleDefault(TxInterceptor.java:253) 12:52:49,355 ERROR [STDERR] at org.jboss.cache.commands.AbstractVisitor.visitGetNodeCommand(AbstractVisitor.java:94) 12:52:49,355 ERROR [STDERR] at org.jboss.cache.commands.read.GetNodeCommand.acceptVisitor(GetNodeCommand.java:42) 12:52:49,355 ERROR [STDERR] at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:142) 12:52:49,355 ERROR [STDERR] at org.jboss.cache.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:157) 12:52:49,356 ERROR [STDERR] at org.jboss.cache.commands.AbstractVisitor.visitGetNodeCommand(AbstractVisitor.java:94) 12:52:49,356 ERROR [STDERR] at org.jboss.cache.commands.read.GetNodeCommand.acceptVisitor(GetNodeCommand.java:42) 12:52:49,356 ERROR [STDERR] at org.jboss.cache.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:142) 12:52:49,356 ERROR [STDERR] at org.jboss.cache.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:155) 12:52:49,357 ERROR [STDERR] at org.jboss.cache.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:108) 12:52:49,357 ERROR [STDERR] at org.jboss.cache.commands.AbstractVisitor.visitGetNodeCommand(AbstractVisitor.java:94) 12:52:49,357 ERROR [STDERR] at org.jboss.cache.commands.read.GetNodeCommand.acceptVisitor(GetNodeCommand.java:42) 12:52:49,358 ERROR [STDERR] at org.jboss.cache.interceptors.InterceptorChain.invoke(InterceptorChain.java:215) 12:52:49,358 ERROR [STDERR] at org.jboss.cache.invocation.CacheInvocationDelegate.getNode(CacheInvocationDelegate.java:420) -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-1082) Optimise nodes for single elements

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1082?page=com.atlassian.jira.p... ] Manik Surtani commented on JBCACHE-1082: ---------------------------------------- Ok, the SingletonMap approach has made things much quicker for writers, due to faster copy-on-write (needed by MVCC) when compared to using a real Map for data. And the memory overhead is much better too. > Optimise nodes for single elements > ---------------------------------- > > Key: JBCACHE-1082 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1082 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.CR1 > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 3.0.0.GA > > Attachments: ReplicatedPojoPerfTest.java, UnversionedNode.patch.txt > > > Many use cases just place a single object in a Node. Rather than going through the memory and performance penalties of using Maps for a single entry, we should: > 1) Create a reference to 2 Objects for key and value, as well as a Map. > 2) Only initialise/construct the Map if Node.putAll() is called, or when Node.put() is called with a second key/value pair > 3) Otherwise just hold the key/value pair as direct object refs. > Would affect UnversionedNode and WorkspaceNodeImpl. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-63) JBossCache benchmarks

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-63?page=com.atlassian.jira.plu... ] Manik Surtani updated JBCACHE-63: --------------------------------- Fix Version/s: (was: 3.0.0.GA) > JBossCache benchmarks > --------------------- > > Key: JBCACHE-63 > URL: https://jira.jboss.org/jira/browse/JBCACHE-63 > Project: JBoss Cache > Issue Type: Task > Affects Versions: 1.2.4SP1 > Reporter: Bela Ban > Assignee: Mircea Markus > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Also bench against other caches -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-63) JBossCache benchmarks

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-63?page=com.atlassian.jira.plu... ] Manik Surtani resolved JBCACHE-63. ---------------------------------- Resolution: Out of Date > JBossCache benchmarks > --------------------- > > Key: JBCACHE-63 > URL: https://jira.jboss.org/jira/browse/JBCACHE-63 > Project: JBoss Cache > Issue Type: Task > Affects Versions: 1.2.4SP1 > Reporter: Bela Ban > Assignee: Mircea Markus > Fix For: 3.0.0.GA > > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Also bench against other caches -- 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

16 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosscache-issues October 2008