January 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1700) TransportConfigurationBuilder.strictPeerToPeer should be false by default

by Galder Zamarreño (Created) (JIRA)

TransportConfigurationBuilder.strictPeerToPeer should be false by default ------------------------------------------------------------------------- Key: ISPN-1700 URL: https://issues.jboss.org/browse/ISPN-1700 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.0.ALPHA1 Reporter: Galder Zamarreño Assignee: Pete Muir Fix For: 5.1.0.FINAL In the old config, global.transport.strictPeerToPeer was false by default. In the new config, TransportConfigurationBuilder has changed the default value to true. This appears to have been done without any specific reason, which smells like a bug. -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] (ISPN-1699) Transactions: Unexpected attribute 'use1PcForAutoCommitTransactions' encountered

by Maarten Gryp (Created) (JIRA)

Transactions: Unexpected attribute 'use1PcForAutoCommitTransactions' encountered --------------------------------------------------------------------------------- Key: ISPN-1699 URL: https://issues.jboss.org/browse/ISPN-1699 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 5.1.0.CR3 Reporter: Maarten Gryp Assignee: Mircea Markus Priority: Blocker <transaction autoCommit="true" use1PcForAutoCommitTransactions="false" lockingMode="OPTIMISTIC"/> results in Message: Unexpected attribute 'use1PcForAutoCommitTransactions' encountered at org.infinispan.configuration.parsing.Parser.parse(Parser.java:105) [infinispan-core-5.1.0.CR3.jar:] at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:365) [infinispan-core-5.1.0.CR3.jar:] at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:349) [infinispan-core-5.1.0.CR3.jar:] at org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:336) [infinispan-core-5.1.0.CR3.jar:] at org.hibernate.cache.infinispan.InfinispanRegionFactory.createCacheManager(InfinispanRegionFactory.java:316) [hibernate-infinispan-4.0.0.Final.jar:] at org.hibernate.cache.infinispan.InfinispanRegionFactory.start(InfinispanRegionFactory.java:268) [hibernate-infinispan-4.0.0.Final.jar:] -- 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, 6 months

5
5
0 / 0

[JBoss JIRA] (ISPN-1673) Max entries logic broken

by Galder Zamarreño (Created) (JIRA)

Max entries logic broken ------------------------ Key: ISPN-1673 URL: https://issues.jboss.org/browse/ISPN-1673 Project: Infinispan Issue Type: Bug Components: Eviction Affects Versions: 5.1.0.CR2 Reporter: Galder Zamarreño Assignee: Vladimir Blagojevic Priority: Blocker Fix For: 5.1.0.CR3 The following test: {code}@Test(groups = "functional", testName = "eviction.MaxEntriesTest") public class MaxEntriesTest extends SingleCacheManagerTest { @Override protected EmbeddedCacheManager createCacheManager() throws Exception { ConfigurationBuilder builder = TestCacheManagerFactory.getDefaultCacheConfiguration(false); builder.eviction().maxEntries(4).strategy(EvictionStrategy.FIFO).build(); return new DefaultCacheManager(builder.build()); } public void test000() { cache.put(1, "1"); assert cache.size() == 1; cache.put(2, "2"); assert cache.size() == 2; cache.put(3, "3"); assert cache.size() == 3 : "Size is: " + cache.size(); } }{code} Fails with: {code}java.lang.AssertionError: Size is: 2{code} @Vladimir, is this related to some of your container changes? -- 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, 6 months

7
8
0 / 0

[JBoss JIRA] (ISPN-1672) Upgrade to Solder 3.1.0.Final

by Kevin Pollet (Created) (JIRA)

Upgrade to Solder 3.1.0.Final ----------------------------- Key: ISPN-1672 URL: https://issues.jboss.org/browse/ISPN-1672 Project: Infinispan Issue Type: Component Upgrade Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet 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, 6 months

5
4
0 / 0

[JBoss JIRA] (ISPN-1701) LegacyGlobalConfigurationAdaptor.adapt(...) fails for null transport

by Paul Ferraro (Created) (JIRA)

LegacyGlobalConfigurationAdaptor.adapt(...) fails for null transport -------------------------------------------------------------------- Key: ISPN-1701 URL: https://issues.jboss.org/browse/ISPN-1701 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.CR3 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Blocker Fix For: 5.1.0.FINAL Calling EmbeddedCacheManager.getCacheManagerConfiguration() fails if the transport is null . Caused by: org.infinispan.CacheException: Caught exception [java.lang.IllegalArgumentException] while invoking method [public void org.jboss.as.clustering.infinispan.subsystem.EmbeddedCacheManagerService.cacheStarted(org.infinispan.notifications.cachemanagerlistener.event.CacheStartedEvent)] on listener instance: org.jboss.as.clustering.infinispan.subsystem.EmbeddedCacheManagerService@3be88133 at org.infinispan.notifications.AbstractListenerImpl$ListenerInvocation$1.run(AbstractListenerImpl.java:204) at org.infinispan.util.concurrent.WithinThreadExecutor.execute(WithinThreadExecutor.java:41) at org.infinispan.notifications.AbstractListenerImpl$ListenerInvocation.invoke(AbstractListenerImpl.java:220) at org.infinispan.notifications.cachemanagerlistener.CacheManagerNotifierImpl.notifyCacheStarted(CacheManagerNotifierImpl.java:121) at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:168) at org.infinispan.CacheImpl.start(CacheImpl.java:496) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:625) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:514) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:528) at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:123) at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:114) at org.hibernate.cache.infinispan.InfinispanRegionFactory.getCache(InfinispanRegionFactory.java:423) at org.hibernate.cache.infinispan.InfinispanRegionFactory.buildEntityRegion(InfinispanRegionFactory.java:187) at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:340) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1737) at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:76) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:905) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:890) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:157) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:81) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] ... 3 more Caused by: java.lang.IllegalArgumentException: Cannot load null class! at org.infinispan.util.Util.getInstance(Util.java:206) at org.infinispan.configuration.global.LegacyGlobalConfigurationAdaptor.adapt(LegacyGlobalConfigurationAdaptor.java:84) at org.infinispan.manager.DefaultCacheManager.getCacheManagerConfiguration(DefaultCacheManager.java:762) at org.jboss.as.clustering.infinispan.subsystem.EmbeddedCacheManagerService.cacheStarted(EmbeddedCacheManagerService.java:210) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_29] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_29] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_29] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_29] at org.infinispan.notifications.AbstractListenerImpl$ListenerInvocation$1.run(AbstractListenerImpl.java:199) ... 25 more -- 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, 6 months

5
5
0 / 0

[JBoss JIRA] (ISPN-1707) Documentation of Distributed Data Stream Processing Framework feature that doesn't appear to be present in actual application

by Andrew Craig (JIRA)

Andrew Craig created ISPN-1707: ---------------------------------- Summary: Documentation of Distributed Data Stream Processing Framework feature that doesn't appear to be present in actual application Key: ISPN-1707 URL: https://issues.jboss.org/browse/ISPN-1707 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.1.0.CR3 Reporter: Andrew Craig Assignee: Manik Surtani Priority: Minor The documentation page [Distributed Data Stream Processing Framework In Infinispan|https://docs.jboss.org/author/display/ISPN/Distributed+Data+St...] is written in a style that describes it as if this feature is already written and implemented that way - however searching through the 5.1.0.CR3 release, I don't see any reference to either {{EntryStreamProcessor}} or {{CoordinatedTask}}, and there's no {{newCoordinatedTask}} method within {{CacheManager}} If this is something that was shelved, shouldn't this page be removed from the documentation and/or flagged as "not actually implemented" I think it would be better placed as a Feature Request JIRA rather than part of the actual user guide? Unless, of course, I'm missing something and it is actually present? -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] (ISPN-1708) Sort out XML parsing testing

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-1708: -------------------------------------- Summary: Sort out XML parsing testing Key: ISPN-1708 URL: https://issues.jboss.org/browse/ISPN-1708 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 5.1.0.FINAL ISPN-1189 is adding yet another XML parsing test and the existing one (org.infinispan.config.parsing.XmlFileParsingTest) doesn't actually test parsing any more. Sort it out... -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] (ISPN-1705) DummyXid should use a better implementation for generating branch and transaction identifiers

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1705: ----------------------------------- Summary: DummyXid should use a better implementation for generating branch and transaction identifiers Key: ISPN-1705 URL: https://issues.jboss.org/browse/ISPN-1705 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 5.1.0.CR3 Reporter: Manik Surtani Assignee: Mircea Markus Priority: Critical Fix For: 5.1.0.FINAL In 5.1.0, the DummyXid was modified to use UUIDs to generate full branch and transaction identifiers. The most and least significant longs of each UUID was used to populate a part of a 64-byte array (the rest of the array being set to 0). This poses a number of problems. 1. Generating 2 UUIDs for each XID is expensive 2. Most of the 64-byte array is set to 0 and wasted 3. XID.hashcode() is implemented by performing Arrays.hashcode on each of the (mostly-empty) 64-bit arrays This makes using the DummyTransactionManager (and consequently, the BatchModeTransactionManager) extremely efficient - if XA compliant. This JIRA proposes to change this such that: 1. Each transaction manager creates a single UUID as a transaction manager ID 2. Each XID created uses an atomic long for transaction and branch ID 3. Combining most and least significant long of the transaction manager ID with the long counter can provide both transaction and branch identifiers. 4. Hashcode should be calculated on the above 3 longs ONLY, not the full array, and should be cached. -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] (ISPN-1703) Upgrade to latest JBoss Marshalling 1.3 bug fix release

by Galder Zamarreño (Created) (JIRA)

Upgrade to latest JBoss Marshalling 1.3 bug fix release ------------------------------------------------------- Key: ISPN-1703 URL: https://issues.jboss.org/browse/ISPN-1703 Project: Infinispan Issue Type: Component Upgrade Components: Marshalling Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.FINAL That is currently 1.3.4.GA which should avoid the issue in the forum post link. -- 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, 6 months

5
4
0 / 0

[JBoss JIRA] (ISPN-1711) NPE when configuring externalizers via XML

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-1711: -------------------------------------- Summary: NPE when configuring externalizers via XML Key: ISPN-1711 URL: https://issues.jboss.org/browse/ISPN-1711 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.CR3 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.FINAL {code}java.lang.NullPointerException at org.infinispan.configuration.global.SerializationConfigurationBuilder.addAdvancedExternalizer(SerializationConfigurationBuilder.java:83) at org.infinispan.configuration.global.LegacyGlobalConfigurationAdaptor.adapt(LegacyGlobalConfigurationAdaptor.java:113) at org.infinispan.manager.DefaultCacheManager.getCacheManagerConfiguration(DefaultCacheManager.java:761) at org.infinispan.configuration.XmlFileParsingTest.assertNamedCacheFile(XmlFileParsingTest.java:90) at org.infinispan.configuration.XmlFileParsingTest.testNamedCacheFile(XmlFileParsingTest.java:86){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, 6 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2012