September 2011 - infinispan-issues

[JBoss JIRA] Created: (ISPN-1387) Update to Hibernate Search 4.0.0.Beta1

by Sanne Grinovero (JIRA)

Update to Hibernate Search 4.0.0.Beta1 -------------------------------------- Key: ISPN-1387 URL: https://issues.jboss.org/browse/ISPN-1387 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Sanne Grinovero -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (ISPN-1385) JDK7 CI job bringing CI to a halt

by Galder Zamarreño (JIRA)

JDK7 CI job bringing CI to a halt --------------------------------- Key: ISPN-1385 URL: https://issues.jboss.org/browse/ISPN-1385 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.2.FINAL The JDK7 job brought CI to an standstill and Jenkins had to be restarted. It's unclear whether this is due to JDK7 itself, or due to the 68MB+ log that the job generates: https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK7-tcp/18/con... The log should be reduced first, try running the testsuite and then enable the job in CI. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (ISPN-302) Enable templated values for manually adding instances via jopr

by Galder Zamarreno (JIRA)

Enable templated values for manually adding instances via jopr -------------------------------------------------------------- Key: ISPN-302 URL: https://jira.jboss.org/jira/browse/ISPN-302 Project: Infinispan Issue Type: Feature Request Components: JMX, reporting and management Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Enable templated values for manually adding instances via jopr >> For manually importing - you should in the plugin descriptor put the JMX-remoting url as >> >> default -- perhaps with the port as XXX, so the user does not have to copy& paste from an >> >> external location, but only click in the text field and replace XXX by the real port. >> >> same for Objectname of the cache manager. > > > > I did that. I told you it did not work and your reply was that it was fragile and you didn't looked into it further... You / we were talking about c:template - which would allow to have several templates -- see jmx-plugin e.g http://git.fedorahosted.org/git/rhq/rht.git?p=rhq/rhq.git;a=blob;f=module... from line 47 on What you can do, an which works is <c:simple-property name="v1Community" type="string" default="public"/> Here the default value 'public' is shown to the user for this property. Sorry that I was confusing things Heiko -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (ISPN-1358) expired entries must be removed with default configuration or <expiration> element

by Dmitry Shohov (JIRA)

expired entries must be removed with default configuration or <expiration> element ---------------------------------------------------------------------------------- Key: ISPN-1358 URL: https://issues.jboss.org/browse/ISPN-1358 Project: Infinispan Issue Type: Enhancement Components: Configuration Affects Versions: 5.0.0.FINAL Reporter: Dmitry Shohov Assignee: Manik Surtani EvictionManagerImpl which removes expired entries by calling purgeExpired() on dataContainer and cacheStore, does not start with default configuration. It requires <eviction> element which has mandatory maxEntries attribute and forces use of bounded cache. Please make it start by default, or if it is not desirable in default configuration make it start with <expiration> element presented in configuration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (ISPN-1381) Continous integration failing due to an issue in JDBC cache store

by Galder Zamarreño (JIRA)

Continous integration failing due to an issue in JDBC cache store ----------------------------------------------------------------- Key: ISPN-1381 URL: https://issues.jboss.org/browse/ISPN-1381 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Assignee: Galder Zamarreño Priority: Blocker Fix For: 5.1.0.ALPHA1 See https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/217/or... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-1333) Add/Remove operations on InterceptorChain are not thread-safe

by Paul Ferraro (JIRA)

Add/Remove operations on InterceptorChain are not thread-safe ------------------------------------------------------------- Key: ISPN-1333 URL: https://issues.jboss.org/browse/ISPN-1333 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 5.0.0.FINAL Reporter: Paul Ferraro Assignee: Manik Surtani Concurrent calls to AdvancedCache.addInterceptor(...) and/or removeInterceptor(...) will result in an faulty interceptor chain. In particular, if calls use an interceptor of the same type, this can cause assertNotAdded to fail inappropriately. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (ISPN-1344) NullpointerException during adding node

by Changgeng Li (JIRA)

NullpointerException during adding node --------------------------------------- Key: ISPN-1344 URL: https://issues.jboss.org/browse/ISPN-1344 Project: Infinispan Issue Type: Bug Reporter: Changgeng Li Assignee: Manik Surtani Detail log file is attached. This happened during adding node. Line 25568: Received the new view Line 25664: NullPointerException is thrown Line 25933: Setting factory enum to %s is printed. 2011-08-24 11:48:52,433 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (OOB-8,erm-cluster-REHASH-TEST,beaumaris-52700) ISPN000136: Execution error java.lang.NullPointerException at org.infinispan.transaction.xa.TransactionFactory.newGlobalTransaction(TransactionFactory.java:260) at org.infinispan.transaction.TransactionTable.getOrCreateLocalTransaction(TransactionTable.java:422) at org.infinispan.interceptors.TxInterceptor.enlist(TxInterceptor.java:227) at org.infinispan.interceptors.TxInterceptor.enlistReadAndInvokeNext(TxInterceptor.java:197) at org.infinispan.interceptors.TxInterceptor.visitLockControlCommand(TxInterceptor.java:157) at org.infinispan.interceptors.DistTxInterceptor.visitLockControlCommand(DistTxInterceptor.java:117) at org.infinispan.commands.control.LockControlCommand.acceptVisitor(LockControlCommand.java:122) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
5
0 / 0

[JBoss JIRA] Updated: (ISPN-61) Transaction 2-phase protocol optimizations

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-61?page=com.atlassian.jira.plugin.sy... ] Mircea Markus updated ISPN-61: ------------------------------ Fix Version/s: 5.1.0.ALPHA2 (was: 5.1.0.ALPHA1) > Transaction 2-phase protocol optimizations > ------------------------------------------ > > Key: ISPN-61 > URL: https://issues.jboss.org/browse/ISPN-61 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 4.0.0.ALPHA4 > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Critical > Fix For: 5.1.0.ALPHA2 , 5.1.0.FINAL > > > Following 2 optimizations might be implemented with respect to transactions. > 1) From an email on infinispan-dev (horizon-dev actually): > if there are only two members int the cluster always use an 1PC. If the 1st phase fails remotely, then also rollback locally. This would reduce one network roundtrip. > While this is an interesting thought, it does raise the potential for race conditions - since this decision will have to be taken in the TxInterceptor in the beforeCompletion phase of a transaction, and by the time the call gets to the interceptor for replication, the topology may have changed such that you need to replicate to 2 instead of 1 other peer. Which would mean a 2PC again. So it does need some thought. > 2) when asked to prepare, a participant might return a value indicating that no changes were made (read-only participant), so this one won't need an commit message, so less roundtrip. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-1340) ReadCommittedLock - commited Cache.remove is not visible to other transactions

by Marcel König (JIRA)

ReadCommittedLock - commited Cache.remove is not visible to other transactions ------------------------------------------------------------------------------ Key: ISPN-1340 URL: https://issues.jboss.org/browse/ISPN-1340 Project: Infinispan Issue Type: Bug Components: Locking and Concurrency Affects Versions: 5.0.0.FINAL Environment: jboss-6.0.0.Final, isolationlevel=READ_COMMITED Reporter: Marcel König Assignee: Manik Surtani Attachments: ReadCommittedLockTest.java See the attached unit test: i added the testVisibilityOfCommittedDataRemove method to your org.infinispan.api.mvcc.read_committed.ReadCommittedLockTest unit test class. This test is successful in infinispan-4.2.1 but not in infinispan-5.0.0. What happens: 1. transaction1(tx1): cache.put("k", "v") 2. tx2: cache.remove("k") 3. tx2: commit 4. tx1: cache.get("k") = "v" What should happen: ... 4. tx1: cache.get("k") = null -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
13
0 / 0

[JBoss JIRA] Created: (ISPN-1371) Add some details to inconsistency warnings around Flag.SKIP_LOCKING

by Sanne Grinovero (JIRA)

Add some details to inconsistency warnings around Flag.SKIP_LOCKING ------------------------------------------------------------------- Key: ISPN-1371 URL: https://issues.jboss.org/browse/ISPN-1371 Project: Infinispan Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 5.1.0.ALPHA1, 5.1.0.BETA1 See ISPN-575; maybe ISPN-1146 too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2011