February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-3641) org.infinispan.util.ThreadLocalLeakTest.testCheckThreadLocalLeaks fails with Azul JDK

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3641?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3641: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Final Resolution: Done > org.infinispan.util.ThreadLocalLeakTest.testCheckThreadLocalLeaks fails with Azul JDK > ------------------------------------------------------------------------------------- > > Key: ISPN-3641 > URL: https://issues.jboss.org/browse/ISPN-3641 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Beta1, 6.0.0.Beta2, 6.0.0.CR1 > Reporter: Vitalii Chepeliuk > Assignee: Dan Berindei > Priority: Minor > Labels: testsuite_stability > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > This is JKD related fail > Error Message > java.lang.NoSuchFieldException: referent > Stacktrace > java.util.concurrent.ExecutionException: java.lang.NoSuchFieldException: referent > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:232) > at java.util.concurrent.FutureTask.get(FutureTask.java:91) > at org.infinispan.util.ThreadLocalLeakTest.testCheckThreadLocalLeaks(ThreadLocalLeakTest.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > 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:662) > Caused by: java.lang.NoSuchFieldException: referent > at java.lang.Class.getDeclaredField(Class.java:1882) > at org.infinispan.util.ThreadLocalLeakTest.findThreadLocalLeaks(ThreadLocalLeakTest.java:143) > at org.infinispan.util.ThreadLocalLeakTest.access$300(ThreadLocalLeakTest.java:35) > at org.infinispan.util.ThreadLocalLeakTest$1.call(ThreadLocalLeakTest.java:76) > at org.infinispan.util.ThreadLocalLeakTest$1.call(ThreadLocalLeakTest.java:61) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > ... 1 > Jenkins job with failed test is here > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-62-ispn-testsuite... -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3881) Remove references to startserver.sh from the documentation

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3881?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3881: ------------------------------- Issue Type: Task (was: Feature Request) > Remove references to startserver.sh from the documentation > ---------------------------------------------------------- > > Key: ISPN-3881 > URL: https://issues.jboss.org/browse/ISPN-3881 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Mircea Markus > Assignee: Tristan Tarrant > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > The 6.0 documentation still contains references to the startserver.sh script. > All these should be removed and replaced with a link to how the servers should be started based on WF. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3863) JDBC and LevelDB cachestore XSD reference removed lockSupportStore

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3863?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3863: ------------------------------- Issue Type: Bug (was: Feature Request) > JDBC and LevelDB cachestore XSD reference removed lockSupportStore > ------------------------------------------------------------------ > > Key: ISPN-3863 > URL: https://issues.jboss.org/browse/ISPN-3863 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 7.0.0.Alpha1 > > -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3862) Upgrade JBoss Marshalling to 1.4.x

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3862?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3862: ------------------------------- Issue Type: Component Upgrade (was: Feature Request) > Upgrade JBoss Marshalling to 1.4.x > ----------------------------------- > > Key: ISPN-3862 > URL: https://issues.jboss.org/browse/ISPN-3862 > Project: Infinispan > Issue Type: Component Upgrade > Components: Marshalling > Reporter: Mircea Markus > Assignee: Dan Berindei > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > This is needed not only for moving to the latest and greatest, but alto in order to align with Wildfly 8. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3964) Move unstable tests to different group

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3964?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3964: ------------------------------- Issue Type: Task (was: Enhancement) > Move unstable tests to different group > -------------------------------------- > > Key: ISPN-3964 > URL: https://issues.jboss.org/browse/ISPN-3964 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core, Test Suite - Query, Test Suite - Server > Affects Versions: 6.0.1.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Labels: testsuite_stability > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > The idea is to move the unstable test to a different test group. This new group will be disabled by default and it would run once a day by CI. -- 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

10 years, 9 months

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.Alpha2 (was: 7.0.0.Alpha1) > 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: Transactions > 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.Alpha2 > > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2034) Add backwards serialization compatibility tests

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2034?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2034: ------------------------------- Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Add backwards serialization compatibility tests > ----------------------------------------------- > > Key: ISPN-2034 > URL: https://issues.jboss.org/browse/ISPN-2034 > Project: Infinispan > Issue Type: Enhancement > Components: Marshalling > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: compatibility > Fix For: 7.0.0.Alpha2 > > > Take each existing minor branch, i.e. 4.1.x, 4.0.x,...etc and modify VersionAwareMarshallerTest so that payloads are stored in a data file. > Then, take data files for each branch and store in git (master and 5.1.x), and try reading them with the existing externalizer/marshalling set up. > It should work... -- 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

10 years, 9 months

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.Alpha2 (was: 7.0.0.Alpha1) > 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 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-833) Revisit cache name predefinition limitation for cache servers

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-833?page=com.atlassian.jira.plugin.s... ] Dan Berindei updated ISPN-833: ------------------------------ Fix Version/s: 7.0.0.Alpha2 (was: 7.0.0.Alpha1) > Revisit cache name predefinition limitation for cache servers > ------------------------------------------------------------- > > Key: ISPN-833 > URL: https://issues.jboss.org/browse/ISPN-833 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > There're are two primary reasons why Infinispan servers require predefined caches to be started up on startup, and do not allow invocations to undefined caches: > 1. Concurrent cache startups were resulting in NPEs (ISPN-635) - This is already solved since the 4.2.x days. > 2. Infinispan has issues dealing with asymmetric clusters (ISPN-658). > Once these two issues have been resolved, revisit the limitation. -- 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

10 years, 9 months

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.Alpha2 (was: 7.0.0.Alpha1) > Silence SuspectExceptions > ------------------------- > > Key: ISPN-2577 > URL: https://issues.jboss.org/browse/ISPN-2577 > Project: Infinispan > Issue Type: Bug > Components: Core > 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.Alpha2 > > > 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2014