December 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3757) User documentation for 6.0 contains links to older versions of Infinispan apidocs

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3757?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3757: ------------------------------- Fix Version/s: 6.0.1.Final > User documentation for 6.0 contains links to older versions of Infinispan apidocs > --------------------------------------------------------------------------------- > > Key: ISPN-3757 > URL: https://issues.jboss.org/browse/ISPN-3757 > Project: Infinispan > Issue Type: Bug > Components: Documentation > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 6.0.1.Final, 7.0.0.Alpha1 > > > All references to apidocs must go to 6.0. Except where linking to an older version is appropriate (upgrade guide might need to). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3752) capacityFactor is not effective

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3752?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3752: ------------------------------- Fix Version/s: 7.0.0.Final 7.0.0.Alpha1 > capacityFactor is not effective > ------------------------------- > > Key: ISPN-3752 > URL: https://issues.jboss.org/browse/ISPN-3752 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 6.0.0.Final > Reporter: Takayoshi Kimura > Assignee: Dan Berindei > Fix For: 6.0.1.Final, 7.0.0.Final, 7.0.0.Alpha1 > > > The capacityFactor is not effective because the ClusterCacheStatus.addMember() uses its own, local joinInfo and doesn't use joiner's capacityFactor on method parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3756) Unnecessary wall clock call for immortal entries

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3756?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3756: ------------------------------- Fix Version/s: 7.0.0.Alpha1 > Unnecessary wall clock call for immortal entries > ------------------------------------------------ > > Key: ISPN-3756 > URL: https://issues.jboss.org/browse/ISPN-3756 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 6.0.1.Final, 7.0.0.Alpha1 > > > When updating immortal entries Infinispan calls up the wall clock time unnecessarily. > {code} > if (e != null) { > e.setValue(v); > InternalCacheEntry original = e; > e = entryFactory.update(e, metadata); > // we have the same instance. So we need to reincarnate. > if (original == e) { > --> e.reincarnate(timeService.wallClockTime()); > } > } else { > // this is a brand-new entry > e = entryFactory.create(k, v, metadata); > } > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3316) CDI Cache interceptor tests are failing while running in EAP container

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3316?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3316: ------------------------------- Fix Version/s: 7.0.0.Alpha1 > CDI Cache interceptor tests are failing while running in EAP container > ---------------------------------------------------------------------- > > Key: ISPN-3316 > URL: https://issues.jboss.org/browse/ISPN-3316 > Project: Infinispan > Issue Type: Bug > Components: CDI integration > Affects Versions: 5.3.0.Final, 6.0.0.Final > Reporter: Anna Manukyan > Assignee: Galder Zamarreño > Labels: 620 > Fix For: 6.0.1.Final, 7.0.0.Alpha1 > > > While migration of the CDI related tests to work under EAP container (at the moment using 6.0.GA), it was found that the tests related to interceptors are failing. The issue relates to > org.infinispan.cdi.test.interceptor.CachePutInterceptorTest, org.infinispan.cdi.test.interceptor.CacheRemoveAllInterceptorTest, org.infinispan.cdi.test.interceptor.CacheRemoveInterceptorTest, org.infinispan.cdi.test.interceptor.CacheResultInterceptorTest. > The failure relates to assertions. The thing is that all actions which are done using javax.cache.cache-api annotations, work properly (I've added some logs e.g. in CachePutInterceptor, and it shows that the data is put to the cache properly). > But later when the test wants to verify that the data is really put to the data, retrieves the cache from the injected CacheContainer, the cache is empty - the data is not there. > The issue appeared since the latest changes to the Infinispan-CDI module, and split to infinispan-jcache module. For the previous version, the tests are passed under EAP container. > The example above was given for the CachePutInterceptorTest, but the same refers to the rest of them. > The git repo for the sources, will be provided later. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3734) Better trace logging with entry versions

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3734?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3734: ------------------------------- Fix Version/s: 6.0.1.Final Affects Version/s: 6.0.0.Final > Better trace logging with entry versions > ---------------------------------------- > > Key: ISPN-3734 > URL: https://issues.jboss.org/browse/ISPN-3734 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 6.0.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Priority: Minor > Fix For: 6.0.1.Final, 7.0.0.Alpha1 > > > These classes do not override the toString method properly: > MetadataImmortalCacheEntry > VersionedCommitCommand > ReadCommittedEntry should add providedMetadata to the trace logging as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3727) intermittent test failure AsyncReplExtendedStatisticTest.testReplaceWithOldVal

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3727?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3727: ------------------------------- Fix Version/s: 6.0.1.Final Affects Version/s: 6.0.0.Final Component/s: Test Suite > intermittent test failure AsyncReplExtendedStatisticTest.testReplaceWithOldVal > ------------------------------------------------------------------------------ > > Key: ISPN-3727 > URL: https://issues.jboss.org/browse/ISPN-3727 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 6.0.0.Final > Reporter: Mircea Markus > Assignee: Pedro Ruivo > Fix For: 6.0.1.Final > > > Failed tests: > AsyncReplExtendedStatisticTest>BaseClusteredExtendedStatisticTest.testReplaceWithOldVal:190->BaseClusteredExtendedStatisticTest.assertCacheValue:253->MultipleCacheManagersTest.assertEventuallyEquals:554->AbstractInfinispanTest.eventually:173->AbstractInfinispanTest.eventually:45->AbstractInfinispanTest.eventually:62 > expected [true] but found [false] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2240) Per-key lock container leads to superfluous TimeoutExceptions on concurrent access to same key

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2240?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2240: ------------------------------- Fix Version/s: 7.0.0.Final 7.0.0.Alpha1 (was: 6.0.1.Final) > Per-key lock container leads to superfluous TimeoutExceptions on concurrent access to same key > ---------------------------------------------------------------------------------------------- > > Key: ISPN-2240 > URL: https://issues.jboss.org/browse/ISPN-2240 > Project: Infinispan > Issue Type: Bug > Components: Locking and Concurrency > Affects Versions: 5.1.6.FINAL, 5.1.x > Reporter: Robert Stupp > Assignee: Mircea Markus > Priority: Critical > Fix For: 7.0.0.Final, 7.0.0.Alpha1 > > Attachments: ISPN-2240_fix_TimeoutExceptions.patch, somehow.zip > > > Hi, > I've encountered a lot of TimeoutExceptions just running a load test against an infinispan cluster. > I tracked down the reason and found out, that the code in org.infinispan.util.concurrent.locks.containers.AbstractPerEntryLockContainer#releaseLock() causes these superfluous TimeoutExceptions. > A small test case (which just prints out timeouts, too late timeouts and "paints" a lot of dots to the console - more dots/second on the console means better throughput ;-) > In a short test I extended the class ReentrantPerEntryLockContainer and changed the implementation of releaseLock() as follows: > {noformat} > public void releaseLock(Object lockOwner, Object key) { > ReentrantLock l = locks.get(key); > if (l != null) { > if (!l.isHeldByCurrentThread()) > throw new IllegalStateException("Lock for [" + key + "] not held by current thread " + Thread.currentThread()); > while (l.isHeldByCurrentThread()) > unlock(l, lockOwner); > if (!l.hasQueuedThreads()) > locks.remove(key); > } > else > throw new IllegalStateException("No lock for [" + key + ']'); > } > {noformat} > The main improvement is that locks are not removed from the concurrent map as long as other threads are waiting on that lock. > If the lock is removed from the map while other threads are waiting for it, they may run into timeouts and force TimeoutExceptions to the client. > The above methods "paints more dots per second" - means: it gives a better throughput for concurrent accesses to the same key. > The re-implemented method should also fix some replication timeout exceptions. > Please, please add this to 5.1.7, if possible. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-1986) Make putForExternalRead return a boolean instead of void

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-1986?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-1986: ------------------------------- Fix Version/s: 7.0.0.Final 7.0.0.Alpha1 (was: 6.0.1.Final) > Make putForExternalRead return a boolean instead of void > -------------------------------------------------------- > > Key: ISPN-1986 > URL: https://issues.jboss.org/browse/ISPN-1986 > Project: Infinispan > Issue Type: Enhancement > Components: Core API > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 7.0.0.Final, 7.0.0.Alpha1 > > > Related to ISPN-1983 and https://hibernate.onjira.com/browse/HHH-7256, I'd like to change the API of putForExternalRead() to return a boolean instead of void. > The reason for doing this is to be able to find out if the PFER did actually end up storing something or not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2577) Silence SuspectExceptions

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2577?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2577: ------------------------------- Fix Version/s: 7.0.0.Final 7.0.0.Alpha1 (was: 6.0.1.Final) > Silence SuspectExceptions > ------------------------- > > Key: ISPN-2577 > URL: https://issues.jboss.org/browse/ISPN-2577 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta4, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.Final, 7.0.0.Alpha1 > > > There are lots of SuspectExceptions in resilience test run: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > We managed to keep these under cover for 5.1.x branch. > This is of course a cosmetic problem, but it polutes the log with unnecessary ERRORs. > Parsed logs here: > http://www.qa.jboss.com/~mlinhard/test_results/run54-parsed/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2255) FineGrainedAtomicMap missing key, value pairs in some cluster nodes in distributed mode, embedded infinispan cache

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2255?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2255: ------------------------------- Fix Version/s: 7.0.0.Final 7.0.0.Alpha1 (was: 6.0.1.Final) > FineGrainedAtomicMap missing key,value pairs in some cluster nodes in distributed mode, embedded infinispan cache > ----------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2255 > URL: https://issues.jboss.org/browse/ISPN-2255 > Project: Infinispan > Issue Type: Bug > Components: Fine-grained API > Affects Versions: 5.1.5.FINAL > Environment: Details about cluster: > 1. Infinispan 5.1.5 > 2. java 7u5 64bit > 3. linux 64bit (two nodes debian and one node ubuntu) > 4. tomcat 7.0.28 > 5. jbossTM 4.16.0 JTA only > Tomcat integration code is here: > https://github.com/zvrablik/tomcatInfinispanSessionManager/tree/master/to... > 6. all machines are on real hw ( no virtual machines), date and time is synchronized and shouldn't vary more than 1 second > Reporter: Zdenek Henek > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 7.0.0.Final, 7.0.0.Alpha1 > > Attachments: fgamissueTest2.zip, jgroupsConfig.xml, sessionInfinispanConfigtestLB.xml > > > I am using FineGrainedAtomicMap to store data into clustering distributed cache. When clustering set to replicated doesn't cause any issues or at least I haven't run > into any. When I switch to distributed mode I don't see some key,value pairs in some nodes. This happens randomly. The numOwners is set to two and I have cluster of three nodes. > more details: > https://community.jboss.org/thread/203420?tstart=60 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2013