December 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2521) org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStoreTest.testPurgeExpiredAllCodepaths fails periodically

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2521?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-2521: ------------------------------------- Assignee: Tristan Tarrant (was: Mircea Markus) > org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStoreTest.testPurgeExpiredAllCodepaths fails periodically > ----------------------------------------------------------------------------------------------------------- > > Key: ISPN-2521 > URL: https://issues.jboss.org/browse/ISPN-2521 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Tristan Tarrant > Labels: testsuite_stability > > The tests are failing in case running testsuite for JDG: > The failure url: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2653) LocalKeyAffinityServiceTest.testFilteredRemoveServers failing randomly

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2653?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2653: ---------------------------------------- TRACE log: http://dl.dropbox.com/u/6148072/testFilteredRemoveServers-0.tgz > LocalKeyAffinityServiceTest.testFilteredRemoveServers failing randomly > ---------------------------------------------------------------------- > > Key: ISPN-2653 > URL: https://issues.jboss.org/browse/ISPN-2653 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 5.2.0.CR1, 5.2.0.Final > > > LocalKeyAffinityServiceTest.testFilteredRemoveServers failing randomly: > {code}testFilteredRemoveServers(org.infinispan.affinity.LocalKeyAffinityServiceTest) Time elapsed: 0.054 sec <<< FAILURE! > java.lang.AssertionError: expected [true] but found [false] > at org.testng.Assert.fail(Assert.java:89) > at org.testng.Assert.failNotEquals(Assert.java:489) > at org.testng.Assert.assertTrue(Assert.java:37) > at org.testng.Assert.assertTrue(Assert.java:47) > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:76) > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:59) > at org.infinispan.affinity.BaseKeyAffinityServiceTest.assertEventualFullCapacity(BaseKeyAffinityServiceTest.java:98) > at org.infinispan.affinity.BaseFilterKeyAffinityServiceTest.assertUnaffected(BaseFilterKeyAffinityServiceTest.java:108) > at org.infinispan.affinity.BaseFilterKeyAffinityServiceTest.testRemoveServers(BaseFilterKeyAffinityServiceTest.java:82) > at org.infinispan.affinity.LocalKeyAffinityServiceTest.testFilteredRemoveServers(LocalKeyAffinityServiceTest.java:66) > 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:680){code} > TRACE log coming up... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2653) LocalKeyAffinityServiceTest.testFilteredRemoveServers failing randomly

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2653: -------------------------------------- Summary: LocalKeyAffinityServiceTest.testFilteredRemoveServers failing randomly Key: ISPN-2653 URL: https://issues.jboss.org/browse/ISPN-2653 Project: Infinispan Issue Type: Bug Components: Distributed Cache Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 5.2.0.CR1, 5.2.0.Final LocalKeyAffinityServiceTest.testFilteredRemoveServers failing randomly: {code}testFilteredRemoveServers(org.infinispan.affinity.LocalKeyAffinityServiceTest) Time elapsed: 0.054 sec <<< FAILURE! java.lang.AssertionError: expected [true] but found [false] at org.testng.Assert.fail(Assert.java:89) at org.testng.Assert.failNotEquals(Assert.java:489) at org.testng.Assert.assertTrue(Assert.java:37) at org.testng.Assert.assertTrue(Assert.java:47) at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:76) at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:59) at org.infinispan.affinity.BaseKeyAffinityServiceTest.assertEventualFullCapacity(BaseKeyAffinityServiceTest.java:98) at org.infinispan.affinity.BaseFilterKeyAffinityServiceTest.assertUnaffected(BaseFilterKeyAffinityServiceTest.java:108) at org.infinispan.affinity.BaseFilterKeyAffinityServiceTest.testRemoveServers(BaseFilterKeyAffinityServiceTest.java:82) at org.infinispan.affinity.LocalKeyAffinityServiceTest.testFilteredRemoveServers(LocalKeyAffinityServiceTest.java:66) 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:680){code} TRACE log coming up... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2652) Create tests covering Dist executors - execution policy

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-2652?page=com.atlassian.jira.plugin.... ] Anna Manukyan updated ISPN-2652: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1530 > Create tests covering Dist executors - execution policy > ------------------------------------------------------- > > Key: ISPN-2652 > URL: https://issues.jboss.org/browse/ISPN-2652 > Project: Infinispan > Issue Type: Task > Components: Distributed Execution and Map/Reduce > Reporter: Anna Manukyan > Assignee: Anna Manukyan > > Add tests covering Dist. exec - execution policy part (with topology aware nodes). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2652) Create tests covering Dist executors - execution policy

by Anna Manukyan (JIRA)

Anna Manukyan created ISPN-2652: ----------------------------------- Summary: Create tests covering Dist executors - execution policy Key: ISPN-2652 URL: https://issues.jboss.org/browse/ISPN-2652 Project: Infinispan Issue Type: Task Components: Distributed Execution and Map/Reduce Reporter: Anna Manukyan Assignee: Anna Manukyan Add tests covering Dist. exec - execution policy part (with topology aware nodes). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2591) Upgrade Server to Infinispan 5.2.0.Beta5

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2591?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2591: ----------------------------------------------- Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug 884793|https://bugzilla.redhat.com/show_bug.cgi?id=884793] ok in 6.1.0.ER6 > Upgrade Server to Infinispan 5.2.0.Beta5 > ---------------------------------------- > > Key: ISPN-2591 > URL: https://issues.jboss.org/browse/ISPN-2591 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2591) Upgrade Server to Infinispan 5.2.0.Beta5

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2591?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2591: ----------------------------------------------- Michal Linhard <mlinhard(a)redhat.com> changed the Status of [bug 884793|https://bugzilla.redhat.com/show_bug.cgi?id=884793] from ON_QA to VERIFIED > Upgrade Server to Infinispan 5.2.0.Beta5 > ---------------------------------------- > > Key: ISPN-2591 > URL: https://issues.jboss.org/browse/ISPN-2591 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node restore

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2632: ----------------------------------------------- Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug 886549|https://bugzilla.redhat.com/show_bug.cgi?id=886549] Illustration of the issue from several hyperion test runs: Elasticity test 8-16-8: http://www.qa.jboss.com/~mlinhard/hyperion3/run0009/report/stats-throughp... Elasticity test 16-32-16: http://www.qa.jboss.com/~mlinhard/hyperion3/run0010/report/stats-throughp... Resilience test 8-7-8: http://www.qa.jboss.com/~mlinhard/hyperion3/run0013/report/stats-throughp... > Uneven request balancing after node restore > -------------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.Beta5 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2550) NoSuchElementException in Hot Rod Encoder

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2550?page=com.atlassian.jira.plugin.... ] Michal Linhard commented on ISPN-2550: -------------------------------------- I've reduced number of entries in the cache during the test to 5000 1kb entries and I've got a clean resilience test run: http://www.qa.jboss.com/~mlinhard/hyperion3/run0013/report/stats-throughp... only expected exceptions: http://www.qa.jboss.com/~mlinhard/hyperion3/run0013/report/loganalysis/se... there is still problem with uneven request balancing (ISPN-2632) and blocking of the whole system after join, when there's more data (5% heap filled), but it doesn't have to be related with issues we're discussing here. > NoSuchElementException in Hot Rod Encoder > ----------------------------------------- > > Key: ISPN-2550 > URL: https://issues.jboss.org/browse/ISPN-2550 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.Beta4 > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Blocker > Fix For: 5.2.0.CR1 > > > Tomas noticed this a while ago in a specific functional test: > https://bugzilla.redhat.com/show_bug.cgi?id=875151 > I'm creating a more general JIRA, cause I'm having this in resilience test. > What I found by quick debug, is that here: > https://github.com/infinispan/infinispan/blob/master/server/hotrod/src/ma... > {code} > for (segmentIdx <- 0 until numSegments) { > val denormalizedSegmentHashIds = allDenormalizedHashIds(segmentIdx) > val segmentOwners = ch.locateOwnersForSegment(segmentIdx) > for (ownerIdx <- 0 until segmentOwners.length) { > val address = segmentOwners(ownerIdx % segmentOwners.size) > val serverAddress = members(address) > val hashId = denormalizedSegmentHashIds(ownerIdx) > log.tracef("Writing hash id %d for %s:%s", hashId, serverAddress.host, serverAddress.port) > writeString(serverAddress.host, buf) > writeUnsignedShort(serverAddress.port, buf) > buf.writeInt(hashId) > } > } > {code} > we're trying to obtain serverAddress for nonexistent address and NoSuchElementException is not handled properly. > It hapens after I kill a node in a resilience test and the exception appears when querying for the node in the members cache. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2651) Default useSynchronization and recovery value changes make tests fail

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2651: -------------------------------------- Summary: Default useSynchronization and recovery value changes make tests fail Key: ISPN-2651 URL: https://issues.jboss.org/browse/ISPN-2651 Project: Infinispan Issue Type: Bug Components: Configuration, Transactions Reporter: Galder Zamarreño Assignee: Mircea Markus Priority: Critical Fix For: 5.2.0.CR1, 5.2.0.Final While investigating ISPN-2054 I've found an important issue wrt default transaction configuration options. First of all, InvocationContextTest.testMishavingListenerResumesContext() is incorrectly coded. It misses the following line after the cache put call to make sure that only exceptional path makes the test pass: {code}fail("Should have failed with an exception");{code} With that in mind, and taking in account that this test uses old programmatic configuration: {code} Configuration cfg = TestCacheManagerFactory.getDefaultConfiguration(true); cfg.setSyncCommitPhase(true); cfg.setSyncRollbackPhase(true); cfg.fluent().transaction().lockingMode(LockingMode.PESSIMISTIC); createClusteredCaches(1, "timestamps", cfg); {code} We should be able to switch it to equivalent new configuration and testMishavingListenerResumesContext should pass: {code} ConfigurationBuilder builder = TestCacheManagerFactory.getDefaultCacheConfiguration(true); builder.transaction() .syncCommitPhase(true).syncRollbackPhase(true) .lockingMode(LockingMode.PESSIMISTIC); createClusteredCaches(1, "timestamps", builder); {code} The problem is that the test does not pass once you switch to equivalent new configuration. It fails with "Should have failed with an exception" message. After debugging, the reason is cos default values in old configuration have been changed for new configuration. To be more precise, in old configuration, defaults are: useSynchronization = false recovery enabled = false In new configuration, equivalent defaults are: useSynchronization = true recovery enabled = true In fact, once you change defaults in new configuration to be both false, the test passes. So, this JIRA must address the following: 1. Why have default values have changed? This is very risky since what should be equivalent configurations externally don't behave the same way. 2. When has these defaults changed and since when has the behaivour changed? 3a. If these new default values are reasonable, documentation must be provided in our upgrade guide section bearing in mind the major version in which the default values changed (see https://docs.jboss.org/author/display/ISPN/Upgrade+Guide). The code should also be documented to note down that some tests might fail which would not otherwise because of change of those default values 3b. If default values should not have changed, they must be reverted and it needs to be checked whether any major release has been out with the default values changed and document it. -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2012