March 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4085) Random failures in StateProviderTest due to race condition

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4085?page=com.atlassian.jira.plugin.... ] Adrian Nistor edited comment on ISPN-4085 at 3/10/14 10:02 AM: --------------------------------------------------------------- If you fix it that way don't they become identical? was (Author: anistor): If you fix it that why don't they become identical? > Random failures in StateProviderTest due to race condition > ---------------------------------------------------------- > > Key: ISPN-4085 > URL: https://issues.jboss.org/browse/ISPN-4085 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 7.0.0.Alpha1 > Environment: jgroups.bind_addr = 127.0.0.1 > java.runtime.version = 1.7.0_51-b13 > java.runtime.name =Java(TM) SE Runtime Environment > java.vm.version = 24.51-b03 > java.vm.vendor = Oracle Corporation > os.name = Mac OS X > os.version = 10.9.2 > sun.arch.data.model = 64 > sun.cpu.endian = little > protocol.stack = null > infinispan.test.jgroups.protocol = tcp > infinispan.unsafe.allow_jdk8_chm = true > java.net.preferIPv4Stack = true > java.net.preferIPv6Stack = null > log4.configuration = null > MAVEN_OPTS = null > Reporter: Gustavo Fernandes > Assignee: Dan Berindei > > In my environment the StateProviderTest .test2() fails sometimes (about 10% of the time) with the following error(s): > {code} > Tests run: 4233, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 428.06 sec <<< FAILURE! > test2(org.infinispan.statetransfer.StateProviderTest) Time elapsed: 0.042 sec <<< FAILURE! > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:92) > at org.junit.Assert.assertTrue(Assert.java:43) > at org.junit.Assert.assertTrue(Assert.java:54) > at org.infinispan.statetransfer.StateProviderTest.test2(StateProviderTest.java:316) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > {code} > The reason why is that test2() feeds the StateProvider a ThreadPoolExecutorService to execute a OutboundTransfer task asynchronously and right after forcing a state transfer > asserts that there is a StateTransfer in progress. Sometimes the executor service manages to execute the task and as a result it clear the ‘transfersByDestination’ map, and thus the test cannot assert that the state transfer is happening > OTOH, the method test1() never fails because it users a mock executor service which never executes the task, so the state transfer map will always contain the outbound task after initiating the state transfer and thus always visible from outside > The quick fix is to also use a mock executor test for the test2() -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4087) MBean registration logging should be at lower level

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4087?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4087: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. Thanks! > MBean registration logging should be at lower level > --------------------------------------------------- > > Key: ISPN-4087 > URL: https://issues.jboss.org/browse/ISPN-4087 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Trivial > Fix For: 7.0.0.Final > > > Whenever the MBeans are registered, an INFO log is printed which is especially annoying in the server startup. This is an internal detail and does not deserve to be INFO -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4086) Use org.jboss.logging.annotations instead of the old deprecated package

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-4086?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-4086: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. Thanks! > Use org.jboss.logging.annotations instead of the old deprecated package > ----------------------------------------------------------------------- > > Key: ISPN-4086 > URL: https://issues.jboss.org/browse/ISPN-4086 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Trivial > Fix For: 7.0.0.Final > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4088) Modify signature of Query/CacheQuery.getResultSize() and related offset/pagination methods to return long

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-4088: ----------------------------------- Summary: Modify signature of Query/CacheQuery.getResultSize() and related offset/pagination methods to return long Key: ISPN-4088 URL: https://issues.jboss.org/browse/ISPN-4088 Project: Infinispan Issue Type: Feature Request Components: Embedded Querying, Remote Querying Affects Versions: 6.0.0.Final Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.0.0.Final The method exists in both new DSL and the classic query api. It should be clarified whether this method and the related pagination methods should use int or long for specifying offsets within the data, also should decide if the total number of results / results per page is a long or an int - and update all involved method signatures to have a unitary treatment of this issue. It appears that recent Lucene versions can offer the number of results as long, while older ones offer it as int (should be verified). This issue was raised in a github conversation here: https://github.com/infinispan/infinispan/pull/2410 -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3944) DistSyncL1RepeatableReadFuncTest.testNoEntryInL1GetWithConcurrentReplace random failures

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3944?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3944: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1074517 > DistSyncL1RepeatableReadFuncTest.testNoEntryInL1GetWithConcurrentReplace random failures > ---------------------------------------------------------------------------------------- > > Key: ISPN-3944 > URL: https://issues.jboss.org/browse/ISPN-3944 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: William Burns > Labels: testsuite_stability > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > Attachments: dsl1rrft.log.gz > > > Random failure in DistSyncL1RepeatableReadFuncTest>DistSyncL1FuncTest.testNoEntryInL1GetWithConcurrentReplace: > {noformat} > 00:23:34,658 ERROR (testng-DistSyncL1RepeatableReadFuncTest:) [UnitTestTestNGListener] Test testNoEntryInL1GetWithConcurrentReplace(org.infinispan.distribution.DistSyncL1RepeatableReadFuncTest) failed. > java.lang.AssertionError: Entry for key [key-to-the-cache] should be in L1 on cache at [NodeA-57647]! > at org.infinispan.distribution.DistributionTestHelper.assertIsInL1(DistributionTestHelper.java:31) > at org.infinispan.distribution.BaseDistFunctionalTest.assertIsInL1(BaseDistFunctionalTest.java:183) > at org.infinispan.distribution.DistSyncL1FuncTest.testNoEntryInL1GetWithConcurrentReplace(DistSyncL1FuncTest.java:193) > {noformat} -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4063) Remove 5.2.x compatibility code from master

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4063?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-4063: -------------------------------------- Assignee: Galder Zamarreño (was: Mircea Markus) > Remove 5.2.x compatibility code from master > ------------------------------------------- > > Key: ISPN-4063 > URL: https://issues.jboss.org/browse/ISPN-4063 > Project: Infinispan > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > All compatibility code with 5.2.x needs to be removed from master. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4063) Remove 5.2.x compatibility code from master

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4063?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4063: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2427 Done with [~NadirX]'s permission :) > Remove 5.2.x compatibility code from master > ------------------------------------------- > > Key: ISPN-4063 > URL: https://issues.jboss.org/browse/ISPN-4063 > Project: Infinispan > Issue Type: Task > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > All compatibility code with 5.2.x needs to be removed from master. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4066) org.infinispan.query.dsl.Query.getResultSize() gives wrong results when used in remote mode

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4066?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4066: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > org.infinispan.query.dsl.Query.getResultSize() gives wrong results when used in remote mode > ------------------------------------------------------------------------------------------- > > Key: ISPN-4066 > URL: https://issues.jboss.org/browse/ISPN-4066 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Labels: 6.3remotequeries, 621 > Fix For: 7.0.0.Final, 7.0.0.Alpha2 > > > It works in embedded mode but not in remote mode. No test case yet for this issue, but it was reported by a user on #infinispan irc. -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4086) Use org.jboss.logging.annotations instead of the old deprecated package

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4086?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4086: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2426 > Use org.jboss.logging.annotations instead of the old deprecated package > ----------------------------------------------------------------------- > > Key: ISPN-4086 > URL: https://issues.jboss.org/browse/ISPN-4086 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Trivial > Fix For: 7.0.0.Final > > -- 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

12 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4087) MBean registration logging should be at lower level

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4087?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4087: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2426 > MBean registration logging should be at lower level > --------------------------------------------------- > > Key: ISPN-4087 > URL: https://issues.jboss.org/browse/ISPN-4087 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Trivial > Fix For: 7.0.0.Final > > > Whenever the MBeans are registered, an INFO log is printed which is especially annoying in the server startup. This is an internal detail and does not deserve to be INFO -- 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

12 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2014