January 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1697) Empty Infinispan config starting transport

by Galder Zamarreño (Created) (JIRA)

Empty Infinispan config starting transport ------------------------------------------ Key: ISPN-1697 URL: https://issues.jboss.org/browse/ISPN-1697 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Assignee: Manik Surtani Note: I think ISPN-1691 and ISPN-1692 will fix this (This failure happens without them applied). Making a note just in case... Running the testsuite I see: {code} <failure message="Unknown warning discovered in file minimal.xml: JOIN(dhcp-144-239-26807) sent to dhcp-144-239-47868 timed out (after 3000 ms), retrying" type="java.lang.AssertionError">java.lang.AssertionError: Unknown warning discovered in file minimal.xml: JOIN(dhcp-144-239-26807) sent to dhcp-144-239-47868 timed out (after 3000 ms), retrying at org.infinispan.config.SampleConfigFilesCorrectnessTest.testConfigWarnings(SampleConfigFilesCorrectnessTest.java:80) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) {code} minimal.xml has no global configuration (nor transport) defined, so why on earth does a JOIN happen? -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (ISPN-1670) cannot view MBeans with attributes in jconsole

by Michal Linhard (Created) (JIRA)

cannot view MBeans with attributes in jconsole ---------------------------------------------- Key: ISPN-1670 URL: https://issues.jboss.org/browse/ISPN-1670 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 5.1.0.CR2 Reporter: Michal Linhard Assignee: Manik Surtani This is a bug in CR3-SNAPSHOT. Version information: {code} ====================== Parameters ====================== ISPN_REPO: git://github.com/infinispan/infinispan.git ISPN_VERSION: 5.1.0-SNAPSHOT ISPN_BRANCH: master IS_TAG: false ==================== last commit: infinispan master ==================== commit afb47efa8e0d9b4db8b1ffb3677be2d12085dac9 Author: Tristan Tarrant <ttarrant(a)redhat.com> Date: Tue Jan 3 16:30:29 2012 +0100 ISPN-1660: Upgrade to Netty 3.2.6.Final {code} When I open a MBean that has attributes in jconsole I get UnmarshallException. MBeans that have only operations, like DistributionManager, RecoveryAdmin work fine. see attached pic. -- 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, 3 months

8
13
0 / 0

[JBoss JIRA] (ISPN-1546) FineGrainedAtomicMap key and value iterators are not threadsafe

by Sanne Grinovero (Created) (JIRA)

FineGrainedAtomicMap key and value iterators are not threadsafe --------------------------------------------------------------- Key: ISPN-1546 URL: https://issues.jboss.org/browse/ISPN-1546 Project: Infinispan Issue Type: Bug Components: Core API, Locking and Concurrency Reporter: Sanne Grinovero Assignee: Manik Surtani Invoking #keySet() or #values() might fail, even when using a transaction to isolate threads: {code} java.util.ConcurrentModificationException at org.infinispan.util.FastCopyHashMap$FasyCopyHashMapIterator.nextEntry(FastCopyHashMap.java:484) at org.infinispan.util.FastCopyHashMap$KeyIterator.next(FastCopyHashMap.java:560) at java.util.AbstractCollection.addAll(AbstractCollection.java:305) at org.infinispan.atomic.FineGrainedAtomicHashMapProxy.keySet(FineGrainedAtomicHashMapProxy.java:104) at org.hibernate.ogm.dialect.infinispan.InfinispanAssociationSnapshot.getRowKeys(InfinispanAssociationSnapshot.java:59) at org.hibernate.ogm.datastore.spi.Association.getKeys(Association.java:132) at org.hibernate.ogm.loader.OgmLoader.getResultSet(OgmLoader.java:420) at org.hibernate.ogm.loader.OgmLoader.doQuery(OgmLoader.java:248) at org.hibernate.ogm.loader.OgmLoader.doQueryAndInitializeNonLazyCollections(OgmLoader.java:215) at org.hibernate.ogm.loader.OgmLoader.loadCollection(OgmLoader.java:185) at org.hibernate.ogm.loader.OgmBasicCollectionLoader.initialize(OgmBasicCollectionLoader.java:42) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:622) at org.hibernate.event.internal.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:82) at org.hibernate.internal.SessionImpl.initializeCollection(SessionImpl.java:1607) at org.hibernate.collection.internal.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:379) at org.hibernate.collection.internal.AbstractPersistentCollection.read(AbstractPersistentCollection.java:112) at org.hibernate.collection.internal.PersistentSet.iterator(PersistentSet.java:180) {code} -- 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, 3 months

10
30
0 / 0

[JBoss JIRA] (ISPN-1690) Fix the inconsitency around the way to enable a sub configuration

by Nicolas Filotto (Created) (JIRA)

Fix the inconsitency around the way to enable a sub configuration ------------------------------------------------------------------ Key: ISPN-1690 URL: https://issues.jboss.org/browse/ISPN-1690 Project: Infinispan Issue Type: Task Components: Core API Affects Versions: 5.1.0.CR2 Reporter: Nicolas Filotto Assignee: Manik Surtani I noticed an inconsistent behavior in the code indeed it is required to call {{builder.invocationBatching().enable()}} or {{builder.jmxStatistics().enable()}}... to enable them but {{builder.transaction().recovery()}} automatically enables the recovery. -- 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, 3 months

7
7
0 / 0

[JBoss JIRA] (ISPN-1656) AS7 Infinispan quickstart not working with latest 5.1 CR

by Galder Zamarreño (Created) (JIRA)

AS7 Infinispan quickstart not working with latest 5.1 CR -------------------------------------------------------- Key: ISPN-1656 URL: https://issues.jboss.org/browse/ISPN-1656 Project: Infinispan Issue Type: Bug Components: CDI integration, Demos and Tutorials Affects Versions: 5.1.0.CR2 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.CR3 AS7 Infinispan quickstart not working with 5.1.0.CR1 nor 5.1.0.CR2. -- 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, 3 months

4
4
0 / 0

[JBoss JIRA] (ISPN-1694) Upgrade to Hibernate Search 4.1.0.Alpha1

by Sanne Grinovero (Created) (JIRA)

Upgrade to Hibernate Search 4.1.0.Alpha1 ---------------------------------------- Key: ISPN-1694 URL: https://issues.jboss.org/browse/ISPN-1694 Project: Infinispan Issue Type: Task Components: Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.1.0.CR3 -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1693) Additional GridFS enhancements and fixes

by Marko Lukša (Created) (JIRA)

Additional GridFS enhancements and fixes ---------------------------------------- Key: ISPN-1693 URL: https://issues.jboss.org/browse/ISPN-1693 Project: Infinispan Issue Type: Enhancement Reporter: Marko Lukša Assignee: Manik Surtani Fix For: 5.1.0.CR3 - Fix resolution of relative & absolute paths ("file.txt" should denote same file as "/file.txt") - GridFile.listFiles(FilenameFilter) invokes filter.accept() with wrong dir - Override GridFile.equals() (java.io.File's implementation is OS-dependent) -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1688) Remove LRU_OLD eviction policy

by Vladimir Blagojevic (Created) (JIRA)

Remove LRU_OLD eviction policy ------------------------------ Key: ISPN-1688 URL: https://issues.jboss.org/browse/ISPN-1688 Project: Infinispan Issue Type: Task Components: Eviction Affects Versions: 5.0.0.FINAL Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 5.1.0.CR3 Along with references to LRU_OLD -- 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, 3 months

3
2
0 / 0

[JBoss JIRA] (ISPN-1649) JDBC cache loader "dropTablesOnExit" does not work

by dex chen (Created) (JIRA)

JDBC cache loader "dropTablesOnExit" does not work -------------------------------------------------- Key: ISPN-1649 URL: https://issues.jboss.org/browse/ISPN-1649 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 5.1.0.CR1 Environment: ISPN 5.1.x, Java 7, H2 DB on Linux Reporter: dex chen Assignee: Manik Surtani I configure my JDBC cache loader with H2 engine using filesystem as store. I set the "dropTablesOnExit" to "true", but I still see the tables/and the data after I stop the cache. Basically, "dropTablesOnExist" has no effect. sample config: <loader class="org.infinispan.loaders.jdbc.stringbased.JdbcStringBasedCacheStore" fetchPersistentState="true" purgeOnStartup="false"> <properties> <property name="stringsTableNamePrefix" value="ISPN_STRING_TABLE"/> <property name="idColumnName" value="ID_COLUMN"/> <property name="dataColumnName" value="DATA_COLUMN"/> <property name="timestampColumnName" value="TIMESTAMP_COLUMN"/> <property name="timestampColumnType" value="BIGINT"/> <property name="connectionFactoryClass" value="org.infinispan.loaders.jdbc.connectionfactory.PooledConnectionFactory"/> <property name="connectionUrl" value="jdbc:h2:file:/tmp/testStore;DB_CLOSE_DELAY=-1"/> <property name="userName" value="sa"/> <property name="driverClass" value="org.h2.Driver"/> <property name="idColumnType" value="VARCHAR(255)"/> <property name="dataColumnType" value="BINARY"/> <property name="dropTableOnExit" value="true"/> <property name="createTableOnStart" value="true"/> </properties> </loader> -- 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, 3 months

5
4
0 / 0

[JBoss JIRA] (ISPN-1657) transaction's use1PcForAutoCommitTransactions property not parsed

by Galder Zamarreño (Created) (JIRA)

transaction's use1PcForAutoCommitTransactions property not parsed ----------------------------------------------------------------- Key: ISPN-1657 URL: https://issues.jboss.org/browse/ISPN-1657 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 5.1.0.CR2 Reporter: Galder Zamarreño Assignee: Mircea Markus Priority: Blocker Fix For: 5.1.0.CR3 Throws: org.infinispan.config.ConfigurationException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[87,7] Message: Unexpected attribute 'use1PcForAutoCommitTransactions' encountered at org.infinispan.configuration.parsing.Parser.parse(Parser.java:103) at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:365) at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:349) at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:336) at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:323) at org.infinispan.test.fwk.TestCacheManagerFactory.fromXml(TestCacheManagerFactory.java:89) at org.infinispan.manager.CacheManagerXmlConfigurationTest.testNamedCacheXML(CacheManagerXmlConfigurationTest.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644) at org.testng.internal.Invoker.invokeMethod(Invoker.java:546) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:700) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1002) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121) at org.testng.TestRunner.runWorkers(TestRunner.java:909) at org.testng.TestRunner.privateRun(TestRunner.java:618) at org.testng.TestRunner.run(TestRunner.java:499) at org.testng.SuiteRunner.runTest(SuiteRunner.java:332) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:327) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:299) at org.testng.SuiteRunner.run(SuiteRunner.java:204) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:915) at org.testng.TestNG.runSuitesLocally(TestNG.java:879) at org.testng.TestNG.run(TestNG.java:787) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:101) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[87,7] Message: Unexpected attribute 'use1PcForAutoCommitTransactions' encountered at org.infinispan.configuration.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:80) at org.infinispan.configuration.parsing.Parser.parseTransaction(Parser.java:262) at org.infinispan.configuration.parsing.Parser.parseCache(Parser.java:210) at org.infinispan.configuration.parsing.Parser.parseNamedCache(Parser.java:159) at org.infinispan.configuration.parsing.Parser.doParse(Parser.java:129) at org.infinispan.configuration.parsing.Parser.parse(Parser.java:92) ... 33 more Process finished with exit code 0 -- 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, 4 months

8
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2012