February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-3958) ReplTopologyChangeTest.testDropServer random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3958?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-3958. -------------------------------- Fix Version/s: 7.0.0.Alpha1 Resolution: Done Fixed by ISPN-3942/ISPN-3845. > ReplTopologyChangeTest.testDropServer random failures > ----------------------------------------------------- > > Key: ISPN-3958 > URL: https://issues.jboss.org/browse/ISPN-3958 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Mircea Markus > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > {{ReplTopologyChangeTest.expectTopologyChange()}} assumes that it will take less than 10 put operations to receive an updated topology after killing a node. Some times, however, that is not enough for the server to send the new topology: > {noformat} > 21:30:46,438 ERROR (testng-ReplTopologyChangeTest:) [UnitTestTestNGListener] Test testDropServer(org.infinispan.client.hotrod.ReplTopologyChangeTest) failed. > java.lang.AssertionError: localhost/127.0.0.1:15269 not found in [/127.0.0.1:15266, /127.0.0.1:15269, /127.0.0.1:15263] expected:<false> but was:<true> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:185) > at org.infinispan.client.hotrod.ReplTopologyChangeTest.expectTopologyChange(ReplTopologyChangeTest.java:141) > at org.infinispan.client.hotrod.ReplTopologyChangeTest.testDropServer(ReplTopologyChangeTest.java:123) > {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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3652) Some tests from org.infinispan.statetransfer package hang on Windows and fails randomly on RHEL and Solaris

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3652?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-3652: ---------------------------------- Assignee: Dan Berindei (was: Mircea Markus) > Some tests from org.infinispan.statetransfer package hang on Windows and fails randomly on RHEL and Solaris > ----------------------------------------------------------------------------------------------------------- > > Key: ISPN-3652 > URL: https://issues.jboss.org/browse/ISPN-3652 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.CR1 > Environment: Windows 2012 && JDK6 > Reporter: Anna Manukyan > Assignee: Dan Berindei > Labels: testsuite_stability > > The tests for the environment specified hang randomly on package org.infinispan.statetransfer. > Due to not being able to login to executing machine at the moment I cannot provide logs/thread dump for the hanged tests. > The logs would be attached later. > Jenkins jobs could be found here > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > Failure description here > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > and here > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3304) ClusterTopologyManagerTest.testClusterRecoveryAfterThreeWaySplit fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3304?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3304: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2371 > ClusterTopologyManagerTest.testClusterRecoveryAfterThreeWaySplit fails randomly > ------------------------------------------------------------------------------- > > Key: ISPN-3304 > URL: https://issues.jboss.org/browse/ISPN-3304 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 5.3.0.Final > Reporter: Pedro Ruivo > Assignee: Mircea Markus > Labels: testsuite_stability > Attachments: ClusterTopologyManagerTest.testClusterRecoveryAfterThreeWaySplit.tar.gz > > > {code:java} > java.lang.RuntimeException: Timed out before caches had complete views. Expected 3 members in each view. Views are as follows: [[ClusterTopologyManagerTest-NodeL-25341], [ClusterTopologyManagerTest-NodeN-52944, ClusterTopologyManagerTest-NodeM-9914], [ClusterTopologyManagerTest-NodeN-52944, ClusterTopologyManagerTest-NodeM-9914]] > at org.infinispan.test.TestingUtil.viewsTimedOut(TestingUtil.java:232) > at org.infinispan.test.TestingUtil.viewsTimedOut(TestingUtil.java:222) > at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:214) > at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:255) > at org.infinispan.statetransfer.ClusterTopologyManagerTest.testClusterRecoveryAfterThreeWaySplit(ClusterTopologyManagerTest.java:156) > ... > {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

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3925) Fix test: ClusterTopologyManagerTest.testClusterRecoveryWithRebalance

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3925?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-3925. -------------------------------- Resolution: Duplicate Issue Duplicate of ISPN-3367 > Fix test: ClusterTopologyManagerTest.testClusterRecoveryWithRebalance > --------------------------------------------------------------------- > > Key: ISPN-3925 > URL: https://issues.jboss.org/browse/ISPN-3925 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Reporter: Sanne Grinovero > Assignee: Dan Berindei > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3367) ClusterTopologyManagerTest.testClusterRecoveryWithRebalance fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3367?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3367: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2371 > ClusterTopologyManagerTest.testClusterRecoveryWithRebalance fails randomly > -------------------------------------------------------------------------- > > Key: ISPN-3367 > URL: https://issues.jboss.org/browse/ISPN-3367 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Alpha1 > Environment: {w2k8r2 OracleJDK1.7}, { RHEL6_x86_64, OracleJDK1.7 and OpenJDK1.7}, {solaris10_x86_64 and solaris10-sparc_x86_64, OracleJDK1.7} > Reporter: Vitalii Chepeliuk > Assignee: Dan Berindei > Labels: testsuite_stability > Attachments: ClusterTopologyManagerTest.log.zip > > > Error Message > Thread already timed out waiting for event merge > Stacktrace > java.lang.IllegalStateException: Thread already timed out waiting for event merge > at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:131) > at org.infinispan.test.fwk.CheckPoint.triggerForever(CheckPoint.java:120) > at org.infinispan.statetransfer.ClusterTopologyManagerTest.testClusterRecoveryWithRebalance(ClusterTopologyManagerTest.java:280) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > Add links to jenkins jobs > windows, OracleJDK1.7>>> > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > Linux, OracleJDK1.7>>> > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > Linux, OpenJDK1.7>>> > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3367) ClusterTopologyManagerTest.testClusterRecoveryWithRebalance fails randomly

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3367?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3367: ------------------------------- Summary: ClusterTopologyManagerTest.testClusterRecoveryWithRebalance fails randomly (was: org.infinispan.statetransfer.ClusterTopologyManagerTest.testClusterRecoveryWithRebalance fails randomly) > ClusterTopologyManagerTest.testClusterRecoveryWithRebalance fails randomly > -------------------------------------------------------------------------- > > Key: ISPN-3367 > URL: https://issues.jboss.org/browse/ISPN-3367 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Alpha1 > Environment: {w2k8r2 OracleJDK1.7}, { RHEL6_x86_64, OracleJDK1.7 and OpenJDK1.7}, {solaris10_x86_64 and solaris10-sparc_x86_64, OracleJDK1.7} > Reporter: Vitalii Chepeliuk > Assignee: Dan Berindei > Labels: testsuite_stability > Attachments: ClusterTopologyManagerTest.log.zip > > > Error Message > Thread already timed out waiting for event merge > Stacktrace > java.lang.IllegalStateException: Thread already timed out waiting for event merge > at org.infinispan.test.fwk.CheckPoint.trigger(CheckPoint.java:131) > at org.infinispan.test.fwk.CheckPoint.triggerForever(CheckPoint.java:120) > at org.infinispan.statetransfer.ClusterTopologyManagerTest.testClusterRecoveryWithRebalance(ClusterTopologyManagerTest.java:280) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > Add links to jenkins jobs > windows, OracleJDK1.7>>> > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > Linux, OracleJDK1.7>>> > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... > Linux, OpenJDK1.7>>> > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3942) HotRod client keep trying recover a connection to a cluster member after shutdown

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3942?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3942: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > HotRod client keep trying recover a connection to a cluster member after shutdown > --------------------------------------------------------------------------------- > > Key: ISPN-3942 > URL: https://issues.jboss.org/browse/ISPN-3942 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Environment: Infinispan server with HotRod client in server-client mode and replicated caches. > Reporter: Wolf-Dieter Fink > Assignee: Pedro Ruivo > Priority: Critical > Labels: clustered, hotrod, hotrod-java-client > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > Attachments: hotrod-client.log > > > If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed. > There is only a replicated cache configured. > From the server-logfile the new cluster view is established > 16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered] > There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server. > This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason. -- 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, 2 months

1
0
0 / 0

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

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3881?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3881: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha1 7.0.0.Final Resolution: Done > Remove references to startserver.sh from the documentation > ---------------------------------------------------------- > > Key: ISPN-3881 > URL: https://issues.jboss.org/browse/ISPN-3881 > Project: Infinispan > Issue Type: Feature Request > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3962) Upgrade to Wildfly 8.0.0.CR1

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-3962: -------------------------------------- Summary: Upgrade to Wildfly 8.0.0.CR1 Key: ISPN-3962 URL: https://issues.jboss.org/browse/ISPN-3962 Project: Infinispan Issue Type: Component Upgrade Components: Test Suite - Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 7.0.0.Alpha1, 7.0.0.Final Upgrade to Wildfly 8.0.0.CR1 and verify whether issues in http://lists.jboss.org/pipermail/infinispan-dev/2014-February/014478.html are gone -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3947) HotRod client keep trying recover connections to a failed cluster

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3947?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3947: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1058887, https://bugzilla.redhat.com/show_bug.cgi?id=1060199 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1058887) > HotRod client keep trying recover connections to a failed cluster > ----------------------------------------------------------------- > > Key: ISPN-3947 > URL: https://issues.jboss.org/browse/ISPN-3947 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Priority: Critical > Labels: hotrod, hotrod-java-client > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > If an infinispan-server cluster is not longer reachable for some reason, i.e. network disconnect, the hot-rod client try to re-establish the lost connections. > The client library will retry this by a fixed calculation based on the max numbers of connections from the pool or 10 multiplied with the number of available servers. > This can lead in a very long time until the application can continue and react as it will wait for the read- or connect-timeout for each try. > To improve this behaviour there should be a configurable limit of retries per server and/or a timeout in total. > This will give the application the chance to handle a remote-cache failure and reply to the user instead of hanging for minutes (with the default settings) -- 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, 2 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