January 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1747) redundant checks in the RecoveryManagerImpl

by Mircea Markus (JIRA)

Mircea Markus created ISPN-1747: ----------------------------------- Summary: redundant checks in the RecoveryManagerImpl Key: ISPN-1747 URL: https://issues.jboss.org/browse/ISPN-1747 Project: Infinispan Issue Type: Enhancement Components: Transactions Affects Versions: 5.0.1.FINAL Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.1.0.FINAL There is a set of unnecessary checks in the RecoveryManagerImpl: a prepared transaction as returned frion RMImpl.getPreparedTransaction can only be remote, so no point in checking weather the tx is local or not. -- 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

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] (ISPN-1743) Allow for "parse configuration, adjust programmatically, register" use case

by Pete Muir (JIRA)

Pete Muir created ISPN-1743: ------------------------------- Summary: Allow for "parse configuration, adjust programmatically, register" use case Key: ISPN-1743 URL: https://issues.jboss.org/browse/ISPN-1743 Project: Infinispan Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir Fix For: 5.1.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

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (ISPN-1739) Topology consistency check in JGroups transport is wrong

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-1739: ------------------------------------- Summary: Topology consistency check in JGroups transport is wrong Key: ISPN-1739 URL: https://issues.jboss.org/browse/ISPN-1739 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.0.CR4 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Critical Fix For: 5.1.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

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] (ISPN-1742) c3p0 settings inside infinispan.xml

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-1742: ---------------------------------- Summary: c3p0 settings inside infinispan.xml Key: ISPN-1742 URL: https://issues.jboss.org/browse/ISPN-1742 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Affects Versions: 5.1.0.CR3 Reporter: Thomas Fromm Assignee: Manik Surtani It would be nice to be able to configure the c3p0 pooling stuff inside the infinispan.xml or in generall as additional properties to the PooledConnectionFactory. e.g. <property name="c3p0.maxPoolSize" value="30"/> -- 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

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (ISPN-1741) Remove old and deprecated pre-5.0 Configuration objects

by Manik Surtani (JIRA)

Manik Surtani created ISPN-1741: ----------------------------------- Summary: Remove old and deprecated pre-5.0 Configuration objects Key: ISPN-1741 URL: https://issues.jboss.org/browse/ISPN-1741 Project: Infinispan Issue Type: Enhancement Components: Configuration Affects Versions: 5.2.0.FINAL Reporter: Manik Surtani Assignee: Vladimir Blagojevic Fix For: 6.0.0.FINAL Remove the deprecated Configuration object altogether from the code base, and update all public APIs and SPIs accordingly. -- 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

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1734) HashConfiguration - rehashWait missing javadoc and xsd doc

by Pete Muir (JIRA)

Pete Muir created ISPN-1734: ------------------------------- Summary: HashConfiguration - rehashWait missing javadoc and xsd doc Key: ISPN-1734 URL: https://issues.jboss.org/browse/ISPN-1734 Project: Infinispan Issue Type: Feature Request Reporter: Pete Muir Assignee: Manik Surtani Fix For: 5.1.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

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1735) StoreAsBinary - all properties missing configuration (javadoc and xsddoc)

by Pete Muir (JIRA)

Pete Muir created ISPN-1735: ------------------------------- Summary: StoreAsBinary - all properties missing configuration (javadoc and xsddoc) Key: ISPN-1735 URL: https://issues.jboss.org/browse/ISPN-1735 Project: Infinispan Issue Type: Feature Request Reporter: Pete Muir Assignee: Manik Surtani Fix For: 5.1.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

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1733) UnsafeConfiguration.unreliableReturnValues missing javadoc and xsddoc

by Pete Muir (JIRA)

Pete Muir created ISPN-1733: ------------------------------- Summary: UnsafeConfiguration.unreliableReturnValues missing javadoc and xsddoc Key: ISPN-1733 URL: https://issues.jboss.org/browse/ISPN-1733 Project: Infinispan Issue Type: Feature Request Reporter: Pete Muir Assignee: Manik Surtani Fix For: 5.1.0.FINAL This is missing on both the UnsafeConfiguration, UnsafeConfigurationBuilder and the xml xsd attribute. -- 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

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] (ISPN-1706) Cannot disable the L1 Cache in some special cases

by Nicolas Filotto (JIRA)

Nicolas Filotto created ISPN-1706: ------------------------------------- Summary: Cannot disable the L1 Cache in some special cases Key: ISPN-1706 URL: https://issues.jboss.org/browse/ISPN-1706 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.1.0.CR3 Reporter: Nicolas Filotto Assignee: Manik Surtani In some specific cases, if we want to define a configuration in which we disabled the L1 cache and the property onRehash, we can still face the following exception: {code} org.infinispan.config.ConfigurationException: Can only move entries to L1 on rehash when L1 is enabled at org.infinispan.config.ConfigurationValidatingVisitor.visitL1Type(ConfigurationValidatingVisitor.java:99) at org.infinispan.config.DelegatingConfigurationVisitor.visitL1Type(DelegatingConfigurationVisitor.java:183) at org.infinispan.config.Configuration$L1Type.accept(Configuration.java:3698) at org.infinispan.config.Configuration$ClusteringType.accept(Configuration.java:2462) at org.infinispan.config.Configuration.accept(Configuration.java:1459) at org.infinispan.manager.DefaultCacheManager.wireCache(DefaultCacheManager.java:655) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:618) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:514) {code} See below a TestCase that represents one way to face this issue: {code} public void testConfig() { GlobalConfigurationBuilder gcb = GlobalConfigurationBuilder.defaultClusteredBuilder(); ConfigurationBuilder cb = new ConfigurationBuilder(); DefaultCacheManager manager = new DefaultCacheManager(gcb.build(), cb.build()); cb = new ConfigurationBuilder(); cb.clustering().cacheMode(CacheMode.DIST_SYNC).l1().disable().disableOnRehash(); manager.defineConfiguration("testConfigCache", cb.build()); manager.getCache("testConfigCache"); } {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

14 years, 2 months

3
7
0 / 0

[JBoss JIRA] (ISPN-1689) ClassCastException due to a bug in LegacyConfigurationAdaptor.adapt

by Nicolas Filotto (Created) (JIRA)

ClassCastException due to a bug in LegacyConfigurationAdaptor.adapt ------------------------------------------------------------------- Key: ISPN-1689 URL: https://issues.jboss.org/browse/ISPN-1689 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.1.0.CR2 Reporter: Nicolas Filotto Assignee: Manik Surtani Priority: Critical Since I upgraded my code to use the new configuration object I realized that the starting time was much slower, after a deeper investigation I realized that the application was stuck at BaseStateTransferManagerImpl.waitForJoinToComplete() because the latch was not released due to the following exception: {code} java.lang.ClassCastException: org.infinispan.remoting.transport.jgroups.JGroupsAddress cannot be cast to org.infinispan.remoting.transport.TopologyAwareAddress at org.infinispan.distribution.ch.TopologyAwareConsistentHash.setCaches(TopologyAwareConsistentHash.java:79) at org.infinispan.distribution.ch.ConsistentHashHelper.createConsistentHash(ConsistentHashHelper.java:114) at org.infinispan.statetransfer.ReplicatedStateTransferManagerImpl.createConsistentHash(ReplicatedStateTransferManagerImpl.java:56) at org.infinispan.statetransfer.BaseStateTransferManagerImpl.prepareView(BaseStateTransferManagerImpl.java:310) at org.infinispan.cacheviews.CacheViewsManagerImpl.handlePrepareView(CacheViewsManagerImpl.java:463) at org.infinispan.cacheviews.CacheViewsManagerImpl.clusterPrepareView(CacheViewsManagerImpl.java:300) at org.infinispan.cacheviews.CacheViewsManagerImpl.clusterInstallView(CacheViewsManagerImpl.java:249) at org.infinispan.cacheviews.CacheViewsManagerImpl$ViewInstallationTask.call(CacheViewsManagerImpl.java:850) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) {code} Then I compared the old configuration with the new configuration and realized that {{org.infinispan.distribution.ch.TopologyAwareConsistentHash}} was wrongly added to my configuration as consistent hash. That is actually because when in {{LegacyConfigurationAdaptor.adapt}} we call {{legacy.getConsistentHashClass()}}, it is set to {{TopologyAwareConsistentHash}} because {{globalConfiguration}} and {{consistentHashClass}} are both null, see below the related code: {code} public String getConsistentHashClass() { if (clustering.hash.consistentHashClass == null) { clustering.hash.consistentHashClass = globalConfiguration == null || globalConfiguration.hasTopologyInfo() ? TopologyAwareConsistentHash.class.getName() : DefaultConsistentHash.class.getName(); } return clustering.hash.consistentHashClass; } {code} In other words any call to {{getConsistentHashClass()}} set the value of {{TopologyAwareConsistentHash}} if it has not been set and unfortunately {{DistributionManagerImpl.start()}} calls it indirectly. -- 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

14 years, 2 months

6
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2012