November 2011 - infinispan-issues

[JBoss JIRA] (ISPN-1553) new configuration should not contain methods that were deprecated in old configuration

by Mircea Markus (Created) (JIRA)

new configuration should not contain methods that were deprecated in old configuration --------------------------------------------------------------------------------------- Key: ISPN-1553 URL: https://issues.jboss.org/browse/ISPN-1553 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.BETA5 Reporter: Mircea Markus Assignee: Pete Muir Fix For: 5.1.0.CR1 E.g. eagerLockingSingleNode was deprecated in the old config. It shouldn't be present in the new config. -- 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
8
0 / 0

[JBoss JIRA] (ISPN-1569) Make configuration elements that were @Dynamic mutable

by Pete Muir (Created) (JIRA)

Make configuration elements that were @Dynamic mutable ------------------------------------------------------ Key: ISPN-1569 URL: https://issues.jboss.org/browse/ISPN-1569 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.BETA5 Reporter: Pete Muir Assignee: Manik Surtani Fix For: 5.1.0.CR1 -- 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
2
0 / 0

[JBoss JIRA] (ISPN-1560) Unsplit api and commons packages back into core

by Tristan Tarrant (Created) (JIRA)

Unsplit api and commons packages back into core ----------------------------------------------- Key: ISPN-1560 URL: https://issues.jboss.org/browse/ISPN-1560 Project: Infinispan Issue Type: Task Reporter: Tristan Tarrant Assignee: Tristan Tarrant Priority: Blocker The split introduced in ISPN-1490 is causing issues due to split packages and the impact this has on OSGi and EAP signed packages. We should revert to the single -core package and do things properly for ISPN-1548 -- 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
3
0 / 0

[JBoss JIRA] (ISPN-1555) locks not being released when transaction doesn't write

by Mircea Markus (Created) (JIRA)

locks not being released when transaction doesn't write ------------------------------------------------------- Key: ISPN-1555 URL: https://issues.jboss.org/browse/ISPN-1555 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 5.1.0.BETA5, 5.1.0.CR1 Reporter: Mircea Markus Assignee: Mircea Markus Priority: Critical tm.begin(); cache.getAdvancedCache().lock("k"); tm.commit(); assertNotLocked("k"); //this fails!!! this transaction doesn't do any write, and we have an optimization in place to skip remote calls if we don't do any write. -- 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
3
0 / 0

[JBoss JIRA] (ISPN-1554) Fix the JDK7 build

by Galder Zamarreño (Created) (JIRA)

Fix the JDK7 build ------------------ Key: ISPN-1554 URL: https://issues.jboss.org/browse/ISPN-1554 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.CR1 Investigate what's wrong with the JDK7 build: {quote}We have noticed the infinispan instance becoming inaccessible/unresponsive due to high CPU (100%) usage. This looks to be exactly the same behavior we saw back in September ... I am able to reproduce this problem by running this job: https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK7-tcp After about 10 minutes of running this job , I saw CPU spike to 100%. I was tailing the console log in my browser at the time, and saw something strange start to happen to the output: https://gist.github.com/9c15057a42b4e330527c It looks as though the first few characters of each line is being chopped off. If you look at the log file on the host in emacs, it looks exactly the same. Ryan Campbell CloudBees, Inc{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, 6 months

4
6
0 / 0

[JBoss JIRA] (ISPN-1552) NPE when starting a cache with the new configuration

by Mircea Markus (Created) (JIRA)

NPE when starting a cache with the new configuration ---------------------------------------------------- Key: ISPN-1552 URL: https://issues.jboss.org/browse/ISPN-1552 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.BETA5 Reporter: Mircea Markus Assignee: Pete Muir Priority: Blocker Fix For: 5.1.0.CR1 This code: ConfigurationBuilder cb = new ConfigurationBuilder(); cb.transaction().use1PcForAutoCommitTransactions(true) .transactionManagerLookup(new DummyTransactionManagerLookup()); DefaultCacheManager cm = new DefaultCacheManager(cb.build()); Throws an exception: java.lang.NullPointerException at org.infinispan.config.ConfigurationValidatingVisitor.visitEvictionType(ConfigurationValidatingVisitor.java:129) at org.infinispan.config.DelegatingConfigurationVisitor.visitEvictionType(DelegatingConfigurationVisitor.java:172) at org.infinispan.config.Configuration$EvictionType.accept(Configuration.java:2878) at org.infinispan.config.Configuration.accept(Configuration.java:1448) at org.infinispan.manager.DefaultCacheManager.wireCache(DefaultCacheManager.java:684) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:647) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:543) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:516) at org.infinispan.tx.Use1PcForInducedTransactionTest.testNewConfigurationCorrectness(Use1PcForInducedTransactionTest.java:80) -- 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
1
0 / 0

[JBoss JIRA] (ISPN-1558) N{

by Pete Muir (Created) (JIRA)

N{ -- Key: ISPN-1558 URL: https://issues.jboss.org/browse/ISPN-1558 Project: Infinispan Issue Type: Bug Reporter: Pete Muir Assignee: Manik Surtani -- 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
2
0 / 0

[JBoss JIRA] (ISPN-1550) typo in AbstractProtocolServer exchanged workerThreads/masterThreads

by Michal Linhard (Created) (JIRA)

typo in AbstractProtocolServer exchanged workerThreads/masterThreads -------------------------------------------------------------------- Key: ISPN-1550 URL: https://issues.jboss.org/browse/ISPN-1550 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.1.0.BETA5 Reporter: Michal Linhard Assignee: Galder Zamarreño Priority: Minor Line 67 in https://github.com/infinispan/infinispan/blob/master/server/core/src/main... -- 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

6
5
0 / 0

[JBoss JIRA] (ISPN-1561) NPE defining named cache

by Pete Muir (Created) (JIRA)

NPE defining named cache ------------------------ Key: ISPN-1561 URL: https://issues.jboss.org/browse/ISPN-1561 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.BETA5 Reporter: Pete Muir Assignee: Pete Muir Fix For: 5.1.0.CR1 {code} DefaultCacheManager cacheManager = new DefaultCacheManager(new ConfigurationBuilder().build()); cacheManager.defineConfiguration("foo", new ConfigurationBuilder().build()); {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
1
0 / 0

[JBoss JIRA] Created: (ISPN-1297) add option to enable 1PC for induced transactions

by Mircea Markus (JIRA)

add option to enable 1PC for induced transactions ------------------------------------------------- Key: ISPN-1297 URL: https://issues.jboss.org/browse/ISPN-1297 Project: Infinispan Issue Type: Feature Request Components: Configuration, Transactions Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.1.0.ALPHA1, 5.1.0.FINAL Starting with Infinispan 5.1 a cache is only able to function in either transactional or non-transactional mode. Mixed mode won't be supported any more. This is causing a backward compatibility issue for existing users that make both transactional and non-transactional access to the same cache. A good example is the Lucene-directory that is writing to a cache through batching API *and* directly. In Lucene-D's case, one can configure autoCommit=true for a transaction: that will induce a transaction within direct (i.e. non transactional) calls. Whilst this preserves backward compatibility, it is not "good enough" as an injected transaction does results in 2 RPCs, one for each phase of 2PC, and that is less performant than the "old" direct call. In order to solve this performance shortcoming, another attribute is to be added: use1PcForInducedTransaction(default to true). Enabling this attribute causes the *induced* transaction to force an 1PC resulting in a single RPC. Other tx that induced one won't be affected by this configuration. This mail thread is also relevant: http://bit.ly/plNbLT -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

8
17
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2011