February 2011 - infinispan-issues

[JBoss JIRA] Created: (ISPN-362) allow pluggable data container in infinispan

by Mircea Markus (JIRA)

allow pluggable data container in infinispan -------------------------------------------- Key: ISPN-362 URL: https://jira.jboss.org/jira/browse/ISPN-362 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani In relation to http://community.jboss.org/message/529586#529586 Users might want to write their own data container and be able to plug that in infinispan. Implementing this would require: - change configuration to support an dataContainer element perhaps under "eviction" elements. This will be passed to DataContainerFacvtory, which will build an instance of the class and pass it back. Actually, in order to allow parameters to this container, it can look like: <eviction wakeUpInterval="500" maxEntries="5000"> <dataContainer class="custom.data.Conatiner"> <properties> <propery name="configParam" value="configValue"/> </properties> </dataContainer> </eviction> -- 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

14 years, 7 months

5
8
0 / 0

[JBoss JIRA] Created: (ISPN-936) putAll suboptimal and possibly wrong

by Mircea Markus (JIRA)

putAll suboptimal and possibly wrong ------------------------------------ Key: ISPN-936 URL: https://issues.jboss.org/browse/ISPN-936 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.2.0.Final Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.2.1.Final, 5.0.0.Final DistributionManager.visitPutMapCommand broadcasts ALL the map entries to ALL the nodes to which keys are mapped. E.g. if Map={k1=v1, k2=v2} and k1 maps to node A, k2 maps to node B then both A and B would receive {k1=v1, k2=v2}. The way it should be is A receives {k1=v1} and B receives {k2=v2}. This is suboptimal and error prone as, by the look of code, both node would store ALL the data in the data container. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-950) Allow users to specify listeners through configurations

by Mircea Markus (JIRA)

Allow users to specify listeners through configurations ------------------------------------------------------- Key: ISPN-950 URL: https://issues.jboss.org/browse/ISPN-950 Project: Infinispan Issue Type: Feature Request Components: Configuration Affects Versions: 5.2.0.Final Reporter: Mircea Markus Assignee: Manik Surtani This would be useful with cache servers as well, as users don't necessarily want to deal with ISPN API for that. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-926) Update wiki with thoughts on Infinispan 2LC as remote cache

by Galder Zamarreño (JIRA)

Update wiki with thoughts on Infinispan 2LC as remote cache ----------------------------------------------------------- Key: ISPN-926 URL: https://issues.jboss.org/browse/ISPN-926 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreño Assignee: Galder Zamarreño Priority: Minor Fix For: 5.0.0.ALPHA3 Update Infinispan 2LC wiki with information from: http://community.jboss.org/message/575814#575814 http://community.jboss.org/message/585841#585841 And some other email threads. Seems like this is being asked regularly now, so also add an FAQ. Making a note of this now cos don't have time to write it right now. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-941) runGuiDemo.bat - Cannot find the declaration of element 'infinispan'.

by Burr Sutter (JIRA)

runGuiDemo.bat - Cannot find the declaration of element 'infinispan'. --------------------------------------------------------------------- Key: ISPN-941 URL: https://issues.jboss.org/browse/ISPN-941 Project: Infinispan Issue Type: Bug Components: Demos and Tutorials Affects Versions: 4.2.1.CR2 Environment: Windows 7 64-bit - 32-bit 1.6 JVM Reporter: Burr Sutter Assignee: Manik Surtani Both sample.xml and gui-demo-cache-config.xml cause the following error: D:\tools\infinispan-4.2.1.CR2\bin>runGuiDemo.bat log4j:WARN No appenders could be found for logger (org.infinispan.config.Infinis panConfiguration). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more in fo. Exception in thread "pool-1-thread-1" java.lang.RuntimeException: java.io.IOExce ption at org.infinispan.demo.InfinispanDemo$10.run(InfinispanDemo.java:355) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.io.IOException at org.infinispan.config.InfinispanConfiguration.newInfinispanConfigurat ion(InfinispanConfiguration.java:264) at org.infinispan.config.InfinispanConfiguration.newInfinispanConfigurat ion(InfinispanConfiguration.java:282) at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager .java:288) at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager .java:273) at org.infinispan.demo.InfinispanDemo$10.run(InfinispanDemo.java:323) ... 3 more Caused by: javax.xml.bind.UnmarshalException - with linked exception: [org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of elemen t 'infinispan'.] at javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalExcept ion(AbstractUnmarshallerImpl.java:315) at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.cr eateUnmarshalException(UnmarshallerImpl.java:503) at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.un marshal0(UnmarshallerImpl.java:204) at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.un marshal(UnmarshallerImpl.java:173) at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnm arshallerImpl.java:120) at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnm arshallerImpl.java:103) at org.infinispan.config.InfinispanConfiguration.newInfinispanConfigurat ion(InfinispanConfiguration.java:256) ... 7 more Caused by: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'infinispan'. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAX ParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(Err orHandlerWrapper.java:131) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError( XMLErrorReporter.java:384) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError( XMLErrorReporter.java:318) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleS tartElement(XMLSchemaValidator.java:1915) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startEl ement(XMLSchemaValidator.java:705) at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerIm pl.startElement(ValidatorHandlerImpl.java:549) at com.sun.xml.internal.bind.v2.runtime.unmarshaller.ValidatingUnmarshal ler.startElement(ValidatingUnmarshaller.java:78) at com.sun.xml.internal.bind.v2.runtime.unmarshaller.SAXConnector.startE lement(SAXConnector.java:137) at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527 ) at org.infinispan.config.parsing.NamespaceFilter.startElement(NamespaceF ilter.java:29) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startEle ment(AbstractSAXParser.java:501) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scan StartElement(XMLNSDocumentScannerImpl.java:400) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSCo ntentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:626) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp l$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3103) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$Prolog Driver.next(XMLDocumentScannerImpl.java:922) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(X MLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next (XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImp l.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X ML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(X ML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser. java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Ab stractSAXParser.java:1205) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333) at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.un marshal0(UnmarshallerImpl.java:200) ... 11 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-935) Make VersionAwareMarshallerTest.testErrorUnmarshalling less vulnerable

by Pete Muir (JIRA)

Make VersionAwareMarshallerTest.testErrorUnmarshalling less vulnerable ---------------------------------------------------------------------- Key: ISPN-935 URL: https://issues.jboss.org/browse/ISPN-935 Project: Infinispan Issue Type: Bug Reporter: Pete Muir Assignee: Manik Surtani Currently depends on implicit class structure which is liable to cause people problems if the class structure changes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-940) Harden release scripts to verify that artifacts work

by Tristan Tarrant (JIRA)

Harden release scripts to verify that artifacts work ---------------------------------------------------- Key: ISPN-940 URL: https://issues.jboss.org/browse/ISPN-940 Project: Infinispan Issue Type: Task Affects Versions: 4.2.1.CR2 Reporter: Tristan Tarrant Assignee: Manik Surtani ISPN-934 shows that the release scripts need a way to check that generated artifacts actually work, and also that the release is performed from the correct branch (e.g. during the 4.2 beta phase releases were made from trunk instead of from the branch) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-934) infinispan-config-4.2.xsd namespace references 5.0

by Tristan Tarrant (JIRA)

infinispan-config-4.2.xsd namespace references 5.0 -------------------------------------------------- Key: ISPN-934 URL: https://issues.jboss.org/browse/ISPN-934 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 4.2.1.CR2 Reporter: Tristan Tarrant Assignee: Manik Surtani Priority: Minor The schema/infinispan-config-4.2.xsd file included in the released JAR has the following header: <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0" targetNamespace="urn:infinispan:config:5.0" xmlns:tns="urn:infinispan:config:5.0" xmlns:xs="http://www.w3.org/2001/XMLSchema"> Where instead it should refer to 4.2. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
9
0 / 0

[JBoss JIRA] Commented: (ISPN-186) Smart L1 cache invalidation

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/ISPN-186?page=com.atlassian.jira.plugin.s... ] Pete Muir commented on ISPN-186: -------------------------------- Initial pull request is at https://github.com/infinispan/infinispan/pull/176 > Smart L1 cache invalidation > --------------------------- > > Key: ISPN-186 > URL: https://issues.jboss.org/browse/ISPN-186 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Manik Surtani > Assignee: Pete Muir > Labels: l1 > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > Need to build a mechanism in which L1 invalidation is NOT multicast, but instead is unicast _if necessary_ to specific nodes that may have cached a given entry. This can be detected by maintaining a list of nodes who have requested a key via a remote get, but this would need to be relayed by all data owners. > Benefits would be performance by removing unnecessary invalidation where this is not needed, and by reducing noise in network stacks of most nodes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-186) Smart L1 cache invalidation

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/ISPN-186?page=com.atlassian.jira.plugin.s... ] Pete Muir commented on ISPN-186: -------------------------------- My impl of this ends up creating a web of unicasts, sending a command to each owner of a key, requesting them to send invalidation commands as required to each node that has cached the key. Because of this, I don't have a single place at which I know the number of nodes to which invalidation will be sent, so can't implement a simple threshold as Bela proposes. Without changing this design (I can't see a lower overhead way to do it, but open to ideas), I think the best way to handle a threshold is to make N = number of invalidations + number of owners but this seems a bit complex. Looking for ideas... > Smart L1 cache invalidation > --------------------------- > > Key: ISPN-186 > URL: https://issues.jboss.org/browse/ISPN-186 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Cache > Reporter: Manik Surtani > Assignee: Pete Muir > Labels: l1 > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > Need to build a mechanism in which L1 invalidation is NOT multicast, but instead is unicast _if necessary_ to specific nodes that may have cached a given entry. This can be detected by maintaining a list of nodes who have requested a key via a remote get, but this would need to be relayed by all data owners. > Benefits would be performance by removing unnecessary invalidation where this is not needed, and by reducing noise in network stacks of most nodes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2011