January 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6031) InfinispanRemoteCacheManagerFactoryBeanTest.setPingOnStartupShouldOverrideDefaultPingOnStartup fails

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6031?page=com.atlassian.jira.plugin.... ] Roman Macor updated ISPN-6031: ------------------------------ Comment: was deleted (was: SpringRemoteCacheManagerFactoryBeanTest.setPingOnStartupShouldOverrideDefaultPingOnStartup fails with the same error.) > InfinispanRemoteCacheManagerFactoryBeanTest.setPingOnStartupShouldOverrideDefaultPingOnStartup fails > ---------------------------------------------------------------------------------------------------- > > Key: ISPN-6031 > URL: https://issues.jboss.org/browse/ISPN-6031 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Reporter: Roman Macor > Assignee: Dan Berindei > Fix For: 8.2.0.Alpha1, 8.1.1.Final > > > Error Message > setPingOnStartup(true) should have overridden property 'transportFactory'. However, it didn't. expected:<true> but was:<null> > Stacktrace > java.lang.AssertionError: setPingOnStartup(true) should have overridden property 'transportFactory'. However, it didn't. expected:<true> but was:<null> > 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.infinispan.spring.support.remote.InfinispanRemoteCacheManagerFactoryBeanTest.setPingOnStartupShouldOverrideDefaultPingOnStartup(InfinispanRemoteCacheManagerFactoryBeanTest.java:394) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > 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.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6068) Upgrade to JGroups 3.6.7.Final

by Dan Berindei (JIRA)

Dan Berindei created ISPN-6068: ---------------------------------- Summary: Upgrade to JGroups 3.6.7.Final Key: ISPN-6068 URL: https://issues.jboss.org/browse/ISPN-6068 Project: Infinispan Issue Type: Component Upgrade Components: Build process Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 8.2.0.Alpha1 Try again to use TCP_NIO2 in the test suite. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6007) Cache.get(...) using Flag.FORCE_WRITE_LOCK should retry on OutdatedTopologyException

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6007?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6007: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3934 > Cache.get(...) using Flag.FORCE_WRITE_LOCK should retry on OutdatedTopologyException > ------------------------------------------------------------------------------------ > > Key: ISPN-6007 > URL: https://issues.jboss.org/browse/ISPN-6007 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.CR1, 8.0.2.Final > Reporter: Paul Ferraro > Assignee: Dan Berindei > Fix For: 8.2.0.Alpha1, 8.1.1.Final > > > From IRC: > pferraro: Following a shutdown of a node, we're seeing OutdatedTopologyExceptions during a Cache.get(...) using Flag.FORCE_WRITE_LOCK when the requested key is not owned by the requesting node > pferraro: is there a reason why Infinispan doesn't automatically retry here? > dberindei: I think we just overlooked it > dberindei: we are retrying a LockControlCommand when you call lock() explicitly > dberindei: but maybe not when it's invoked for a get() > pferraro_: is that something that can be fixed easily? > dberindei: yes, I think so -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6007) Cache.get(...) using Flag.FORCE_WRITE_LOCK should retry on OutdatedTopologyException

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6007?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-6007: ------------------------------- Fix Version/s: 8.1.1.Final (was: 8.0.3.Final) > Cache.get(...) using Flag.FORCE_WRITE_LOCK should retry on OutdatedTopologyException > ------------------------------------------------------------------------------------ > > Key: ISPN-6007 > URL: https://issues.jboss.org/browse/ISPN-6007 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.0.CR1, 8.0.2.Final > Reporter: Paul Ferraro > Assignee: Dan Berindei > Fix For: 8.2.0.Alpha1, 8.1.1.Final > > > From IRC: > pferraro: Following a shutdown of a node, we're seeing OutdatedTopologyExceptions during a Cache.get(...) using Flag.FORCE_WRITE_LOCK when the requested key is not owned by the requesting node > pferraro: is there a reason why Infinispan doesn't automatically retry here? > dberindei: I think we just overlooked it > dberindei: we are retrying a LockControlCommand when you call lock() explicitly > dberindei: but maybe not when it's invoked for a get() > pferraro_: is that something that can be fixed easily? > dberindei: yes, I think so -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6066) HotRodServerConfigurationBuilder.build() mutates the builder

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6066?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6066: ------------------------------ Component/s: Server > HotRodServerConfigurationBuilder.build() mutates the builder > ------------------------------------------------------------ > > Key: ISPN-6066 > URL: https://issues.jboss.org/browse/ISPN-6066 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.1.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > > When HotRodServerConfigurationBuilder.build() calls validate(), and proxyHost/proxyPort is not set, it sets its value. That causes problems if you call build() once, (throw away the configuration) and reset host/port to different value - proxyHost/proxyPort is already set, although the user thinks that it's at its defaults (the same as host/port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6067) ClientAsymmetricClusterTest broken

by Radim Vansa (JIRA)

Radim Vansa created ISPN-6067: --------------------------------- Summary: ClientAsymmetricClusterTest broken Key: ISPN-6067 URL: https://issues.jboss.org/browse/ISPN-6067 Project: Infinispan Issue Type: Bug Components: Remote Protocols Affects Versions: 8.1.0.Final Reporter: Radim Vansa When the TransportObjectFactory is created, it executes a first ping in which it gets the topology. When the test tries to retrieve cache 'asymmetricCache' which is defined only on one node, another ping is executed, checking the presence of this cache. However, the ping can go to any node, and therefore it may fail to retrieve the cache and cache manager returns null, which results in NPE in the test. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6066) HotRodServerConfigurationBuilder.build() mutates the builder

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6066?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6066: ------------------------------ Status: Open (was: New) > HotRodServerConfigurationBuilder.build() mutates the builder > ------------------------------------------------------------ > > Key: ISPN-6066 > URL: https://issues.jboss.org/browse/ISPN-6066 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > > When HotRodServerConfigurationBuilder.build() calls validate(), and proxyHost/proxyPort is not set, it sets its value. That causes problems if you call build() once, (throw away the configuration) and reset host/port to different value - proxyHost/proxyPort is already set, although the user thinks that it's at its defaults (the same as host/port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6066) HotRodServerConfigurationBuilder.build() mutates the builder

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6066?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6066: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3933 > HotRodServerConfigurationBuilder.build() mutates the builder > ------------------------------------------------------------ > > Key: ISPN-6066 > URL: https://issues.jboss.org/browse/ISPN-6066 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > > When HotRodServerConfigurationBuilder.build() calls validate(), and proxyHost/proxyPort is not set, it sets its value. That causes problems if you call build() once, (throw away the configuration) and reset host/port to different value - proxyHost/proxyPort is already set, although the user thinks that it's at its defaults (the same as host/port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6066) HotRodServerConfigurationBuilder.build() mutates the builder

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-6066?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-6066: ------------------------------ Affects Version/s: 8.1.0.Final > HotRodServerConfigurationBuilder.build() mutates the builder > ------------------------------------------------------------ > > Key: ISPN-6066 > URL: https://issues.jboss.org/browse/ISPN-6066 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > > When HotRodServerConfigurationBuilder.build() calls validate(), and proxyHost/proxyPort is not set, it sets its value. That causes problems if you call build() once, (throw away the configuration) and reset host/port to different value - proxyHost/proxyPort is already set, although the user thinks that it's at its defaults (the same as host/port). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5727) Client Listener removal and shutdown problems

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5727?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5727: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1297930|https://bugzilla.redhat.com/show_bug.cgi?id=1297930] from NEW to POST > Client Listener removal and shutdown problems > --------------------------------------------- > > Key: ISPN-5727 > URL: https://issues.jboss.org/browse/ISPN-5727 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.0.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.1.0.Final, 8.0.2.Final > > > There are a couple of problems related to client listener registration on the client: > 1. When shutting down a remote cache manager to which client listeners have been added, even if the user does not remove them individually, stopping the remote cache manager should shutdown all client-side client listener threads. This is not the case right now. > 2. When removing a client listener, the client listener thread needs to be stopped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2016