February 2012 - infinispan-issues

[JBoss JIRA] (ISPN-1870) Document FileSync options in the FileCacheStore

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1870: ----------------------------------- Summary: Document FileSync options in the FileCacheStore Key: ISPN-1870 URL: https://issues.jboss.org/browse/ISPN-1870 Project: Infinispan Issue Type: Task Components: Loaders and Stores Affects Versions: 5.1.1.FINAL Reporter: Manik Surtani Assignee: Galder Zamarreño Fix For: 5.1.2.CR1, 5.1.2.FINAL We need to: 1. Log which FileSync is being used when the FileCacheStore starts up 2. Document the different FileSync options available and what they do, in the User Guide ( https://docs.jboss.org/author/display/ISPN/Home and https://docs.jboss.org/author/display/ISPN51/Home ) -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] (ISPN-1861) Add a toString() method on configuration objects

by Christophe Domas (JIRA)

Christophe Domas created ISPN-1861: -------------------------------------- Summary: Add a toString() method on configuration objects Key: ISPN-1861 URL: https://issues.jboss.org/browse/ISPN-1861 Project: Infinispan Issue Type: Enhancement Components: Configuration Affects Versions: 5.1.1.FINAL Reporter: Christophe Domas Assignee: Manik Surtani Priority: Minor I'm using fluent builders for programmatically configure infinspan and a toString() method should have help me to see that write-behind was not activated with async() method (there's an error in https://docs.jboss.org/author/display/ISPN/Configuring+cache+programmatic... - see my comment in this page) -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] (ISPN-1846) Use correct version of Transactions API

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-1846: ------------------------------------- Summary: Use correct version of Transactions API Key: ISPN-1846 URL: https://issues.jboss.org/browse/ISPN-1846 Project: Infinispan Issue Type: Component Upgrade Affects Versions: 5.1.1.FINAL, 5.1.0.FINAL Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL As discuseed on mailing list: >From Pete Muir: {quote} On 7 Feb 2012, at 14:22, Sanne Grinovero wrote: > I'm having the transactions API defined by both the following packages: > > Hibernate core depends on: > > <parent> > <groupId>org.jboss.spec</groupId> > <artifactId>jboss-specs-parent</artifactId> > <version>1.0.0.Beta2</version> > </parent> > <groupId>org.jboss.spec.javax.transaction</groupId> > <artifactId>jboss-transaction-api_1.1_spec</artifactId> > <version>1.0.0.Final</version> This is the new (correct) location. > > Infinispan core depends on: > > <parent> > <groupId>org.jboss.javaee</groupId> > <artifactId>jboss-javaee-parent</artifactId> > <version>5.2.0.Beta1</version> > </parent> > <groupId>org.jboss.javaee</groupId> > <artifactId>jboss-transaction-api</artifactId> > <version>1.0.1.GA</version> > > I'd like to introduce some consistency, especially since some project use both. > Which one should we use ? This is way out of date. > > AS 7.1 [master] > is using > <dependency> > <groupId>org.jboss.spec.javax.transaction</groupId> > <artifactId>jboss-transaction-api_1.1_spec</artifactId> > <version>1.0.0.Final</version> > </dependency> > > So I guess Infinispan should pick the same? {quote} -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] (ISPN-1860) HotRod client topology info can get out of sync with the server topology info

by Dan Berindei (JIRA)

Dan Berindei created ISPN-1860: ---------------------------------- Summary: HotRod client topology info can get out of sync with the server topology info Key: ISPN-1860 URL: https://issues.jboss.org/browse/ISPN-1860 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.1.1.FINAL Reporter: Dan Berindei Assignee: Manik Surtani Fix For: 5.2.0.FINAL Say we have a HotRod cluster with a JGroups view A1 [A, B]. A client makes a get request to A, and it receives topology id 1, with nodes [A, B]. Another node C joins the HotRod cluster, and the JGroups view becomes A2 [A, B, C]. It takes a certain time for C to finish joining the topology cache, so for a limited amount of time the topology cache on A only contains [A, B]. If the client makes another get request during this time interval, it will receive topology id 2, but still with nodes [A, B]. So its consistent hash will not contain C. Future requests from the same client will send topology id 2 to the server, so the server will believe that the client's CH is [A, B, C] and won't send another topology update until another JGroups view is installed (because of a join, leave, or merge). Note that this can happen even if the client had C in its initial host list, because topology updates override the initial host list. -- 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, 2 months

3
10
0 / 0

[JBoss JIRA] (ISPN-1866) org.infinispan.configuration.cache.Configuration missing toString() implementation

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created ISPN-1866: ----------------------------------------- Summary: org.infinispan.configuration.cache.Configuration missing toString() implementation Key: ISPN-1866 URL: https://issues.jboss.org/browse/ISPN-1866 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.1.FINAL Reporter: Richard Achmatowicz Assignee: Manik Surtani Priority: Minor I'd like to be able to dump the entire Configuration to see how the full configuration has been configured. Dumping individual parts of the configuration to a String would also be nice. -- 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, 2 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1859) CacheManager.defineConfiguration override doesn't work for hash configuration values

by William Burns (JIRA)

William Burns created ISPN-1859: ----------------------------------- Summary: CacheManager.defineConfiguration override doesn't work for hash configuration values Key: ISPN-1859 URL: https://issues.jboss.org/browse/ISPN-1859 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.1.FINAL Reporter: William Burns Assignee: Manik Surtani While testing some stuff for ISPN-1837, I found that the hash configuration for DIST doesn't override properly when using the defineConfiguration method on the DefaultCacheManager. The problem is that the OverrideConfigurationVisitor doesn't copy over the activated value, so when the config is copied it over it doesn't think the hash configuration was touched and subsequently skips it. The interesting thing is that L1 should also be broken, but because of how the LegacyConfigurationAdaptor works it actually activates L1 no matter what, since it will either enable or disable it. Also the override works properly if the default has a setting for the hash configuration. I have a testNG that very easily shows this. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] (ISPN-1864) Convert externalizer configuration tests to new configuration

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-1864: -------------------------------------- Summary: Convert externalizer configuration tests to new configuration Key: ISPN-1864 URL: https://issues.jboss.org/browse/ISPN-1864 Project: Infinispan Issue Type: Enhancement Components: Configuration, Marshalling Reporter: Galder Zamarreño Assignee: Galder Zamarreño Priority: Minor Fix For: 5.2.0.ALPHA1 Convert externalizer configuration tests to new 5.1 configuration. Done while investigating the forum post. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1868) enable() method is missing after async() in "ConfigurationBuilder Programmatic Configuration API"

by Christophe Domas (JIRA)

Christophe Domas created ISPN-1868: -------------------------------------- Summary: enable() method is missing after async() in "ConfigurationBuilder Programmatic Configuration API" Key: ISPN-1868 URL: https://issues.jboss.org/browse/ISPN-1868 Project: Infinispan Issue Type: Bug Components: Demos and Tutorials Affects Versions: 5.1.1.FINAL Reporter: Christophe Domas Assignee: Manik Surtani In doc: https://docs.jboss.org/author/display/ISPN/Configuring+cache+programmatic... section: "Configuring Infinispan with one or several chained persistent stores is simple too:" I think enable() is missing after async() in the following code (with infinispan-5.1.1): actual doc: {code} Configuration config = new ConfigurationBuilder() .loaders() .shared(false).passivation(false).preload(false) .addFileCacheStore().location("/tmp").streamBufferSize(1800).async().threadPoolSize(20).build(); {code} corrected doc: {code} Configuration config = new ConfigurationBuilder() .loaders() .shared(false).passivation(false).preload(false) .addFileCacheStore().location("/tmp").streamBufferSize(1800).async().enable().threadPoolSize(20).build(); {code} I added a comment on the page you can remove (I spent so much time to understand why it didn't works that I've filled a ticket to ask for toString() methods in configuration objects: ISPN-1861) -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1812) Upgrade to JGroups 3.1.x

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-1812: ----------------------------------------- Summary: Upgrade to JGroups 3.1.x Key: ISPN-1812 URL: https://issues.jboss.org/browse/ISPN-1812 Project: Infinispan Issue Type: Component Upgrade Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] (ISPN-1853) JMX documentation packaged correctly

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-1853: -------------------------------------- Summary: JMX documentation packaged correctly Key: ISPN-1853 URL: https://issues.jboss.org/browse/ISPN-1853 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.1.FINAL Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 5.1.2.CR1, 5.1.2.FINAL, 5.2.0.ALPHA1 http://docs.jboss.org/infinispan/5.1/apidocs/jmxComponents.html is empty. In the build, I have: {code}[g@dhcp-144-239:~/Go/upstream/old/infinispan-5.1.1.FINAL.git]% (master) fndany jmxComponents ./target/distribution/infinispan-5.1.1.FINAL/doc/5.1/apidocs/jmxComponents.html ./target/site/apidocs/jmxComponents.html{code} The first html file is empty and the second contains the right data. So, something goes wrong when building the distribution. -- 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, 2 months

3
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2012