April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8941) RemoteCacheAdmin configuration name should use cache name

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-8941?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-8941: --------------------------------- Issue Type: Bug (was: Enhancement) Reclassifying as an actual bug, there is no way to customize the name in org.infinispan.configuration.cache.Configuration; the name is written out org.infinispan.client.hotrod.impl.RemoteCacheManagerAdminImpl#getOrCreateCache(java.lang.String, org.infinispan.commons.configuration.BasicConfiguration). So this is a breaking change as well. Wrapping org.infinispan.commons.configuration.BasicConfiguration in a fashion to woarkound hotrod logic {code} @Override public String toXMLString(String name) { ParserRegistry reg = new ParserRegistry(); return reg.serialize("configuration", configuration); }{code} breaks compatibility with future versions. > RemoteCacheAdmin configuration name should use cache name > --------------------------------------------------------- > > Key: ISPN-8941 > URL: https://issues.jboss.org/browse/ISPN-8941 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Hot Rod, Server > Affects Versions: 9.2.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.1.Final > > > The current implementation of the server-side for remote cache admin expects the name of the configuration in the supplied XML to be "configuration" . This would be more intuitive if it used the actual name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8998) Automatically release from CI

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-8998?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on ISPN-8998: -------------------------------------- The testing of this is polluting tags on master github repo :-( * [new tag] 0.0.1.Qualifier -> 0.0.1.Qualifier > Automatically release from CI > ----------------------------- > > Key: ISPN-8998 > URL: https://issues.jboss.org/browse/ISPN-8998 > Project: Infinispan > Issue Type: Bug > Components: Build, CI > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > The releases should happen via a Jenkins job: > * versioning, build and stage to nexus > * reversion and build of simple tutorials against stage repository to ensure that all artifacts are correctly published > * release and drop of nexus staging repo > * push tag and bump version to next snapshot on master branch -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9090) Create both thin and fat servers

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-9090: ------------------------------------- Summary: Create both thin and fat servers Key: ISPN-9090 URL: https://issues.jboss.org/browse/ISPN-9090 Project: Infinispan Issue Type: Bug Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.3.0.Alpha1 The server build should create two servers: * a thin one (to be pushed to maven and used for the testsuite) * a fat one (to be used as the binary distro) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9089) Conflict Resolution phase should be non-blocking and restart on node failures

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9089?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9089: ------------------------------- Status: Open (was: New) > Conflict Resolution phase should be non-blocking and restart on node failures > ----------------------------------------------------------------------------- > > Key: ISPN-9089 > URL: https://issues.jboss.org/browse/ISPN-9089 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Alpha1 > > > Currently if a node crashes during the conflict resolution phase, all topology updates and rebalancing is blocked until CR times out. As the CR timeout is the state transfer timeout, this means the cluster is in limbo for 4 minutes by default. This blocking behaviour occurs because currently the entire CR phase is executed in the merge thread, however it should occur asynchronously in a similar manner to a cache rebalance with CR restarting in the event of nodes leaving. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9089) Conflict Resolution phase should be non-blocking and restart on node failures

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9089?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9089: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5902 > Conflict Resolution phase should be non-blocking and restart on node failures > ----------------------------------------------------------------------------- > > Key: ISPN-9089 > URL: https://issues.jboss.org/browse/ISPN-9089 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Alpha1 > > > Currently if a node crashes during the conflict resolution phase, all topology updates and rebalancing is blocked until CR times out. As the CR timeout is the state transfer timeout, this means the cluster is in limbo for 4 minutes by default. This blocking behaviour occurs because currently the entire CR phase is executed in the merge thread, however it should occur asynchronously in a similar manner to a cache rebalance with CR restarting in the event of nodes leaving. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9089) Conflict Resolution phase should be non-blocking and restart on node failures

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-9089: ---------------------------------- Summary: Conflict Resolution phase should be non-blocking and restart on node failures Key: ISPN-9089 URL: https://issues.jboss.org/browse/ISPN-9089 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 9.2.1.Final Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 9.3.0.Alpha1 Currently if a node crashes during the conflict resolution phase, all topology updates and rebalancing is blocked until CR times out. As the CR timeout is the state transfer timeout, this means the cluster is in limbo for 4 minutes by default. This blocking behaviour occurs because currently the entire CR phase is executed in the merge thread, however it should occur asynchronously in a similar manner to a cache rebalance with CR restarting in the event of nodes leaving. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9036) Parameterized branding for C++

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9036?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9036: ------------------------------------- Status: Open (was: New) > Parameterized branding for C++ > ------------------------------ > > Key: ISPN-9036 > URL: https://issues.jboss.org/browse/ISPN-9036 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Vittorio Rigamonti > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9036) Parameterized branding for C++

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9036?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9036: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/cpp-client/pull/330 > Parameterized branding for C++ > ------------------------------ > > Key: ISPN-9036 > URL: https://issues.jboss.org/browse/ISPN-9036 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Vittorio Rigamonti > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8719) KeySet.(iterator|spliterator|stream) not compatible with versions before 9.1

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8719?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8719: -------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/5896, https://github.com/infinispan/infinispan/pull/5903, https://github.com/infinispan/infinispan/pull/5926, https://github.com/infinispan/infinispan/pull/5927, https://github.com/infinispan/infinispan/pull/5928 (was: https://github.com/infinispan/infinispan/pull/5896, https://github.com/infinispan/infinispan/pull/5903) > KeySet.(iterator|spliterator|stream) not compatible with versions before 9.1 > ---------------------------------------------------------------------------- > > Key: ISPN-8719 > URL: https://issues.jboss.org/browse/ISPN-8719 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.0.Final, 9.2.0.Final > Reporter: Marek Posolda > Assignee: William Burns > Priority: Critical > Fix For: 9.1.8.Final, 9.2.2.Final, 9.3.0.Alpha1 > > Attachments: InfinispanRemote.java > > > Steps to reproduce: > 1) Use infinispan server version 8.2.6 (or JDG server 7.1.0) and start it. > {code} > cd JDG_HOME/bin > ./standalone.sh > {code} > 2) Create sample java project having dependency on latest dependency 9.2.0.CR1 in pom.xml: > {code} > <dependencies> > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-core</artifactId> > <version>9.2.0.CR1</version> > </dependency> > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-cachestore-remote</artifactId> > <version>9.2.0.CR1</version> > </dependency> > </dependencies> > {code} > 3) Add one simple java class based on the tutorial: http://infinispan.org/tutorials/simple/remote/ . The only difference is that I use hotRod protocolVersion 2.5 and calling: > {code} > remoteCache.keySet().iterator().hasNext() > {code}. I am attaching the class in attachement. > 4) Run the class. Seeing exception in both server log and on client-side. > Server exception > {code} > 10:44:20,365 ERROR [org.infinispan.server.hotrod.CacheDecodeContext] (HotRodServerWorker-6-1) ISPN005003: Exception reported: java.lang.IllegalStateException: ISPN006016: Factory 'org.infinispan.server.hotrod.HotRodServer$ToEmptyBytesKeyValueFilterConverter' not found in server > at org.infinispan.server.hotrod.iteration.DefaultIterationManager.getFactory(DefaultIterationManager.java:148) > at org.infinispan.server.hotrod.iteration.DefaultIterationManager.start(DefaultIterationManager.java:131) > at org.infinispan.server.hotrod.ContextHandler.realRead(ContextHandler.java:175) > at org.infinispan.server.hotrod.ContextHandler.lambda$channelRead0$1(ContextHandler.java:57) > at org.infinispan.server.hotrod.ContextHandler$$Lambda$86/1492247987.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) > at java.lang.Thread.run(Thread.java:745) > {code} > Client exception: > {code} > Jan 24, 2018 10:44:20 AM org.infinispan.client.hotrod.impl.protocol.Codec20 checkForErrorsInResponseStatus > WARN: ISPN004005: Error received from the server: java.lang.IllegalStateException: ISPN006016: Factory 'org.infinispan.server.hotrod.HotRodServer$ToEmptyBytesKeyValueFilterConverter' not found in server > Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=5 returned server error (status=0x85): java.lang.IllegalStateException: ISPN006016: Factory 'org.infinispan.server.hotrod.HotRodServer$ToEmptyBytesKeyValueFilterConverter' not found in server > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:408) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:162) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:148) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) > at org.infinispan.client.hotrod.impl.operations.IterationStartOperation.executeOperation(IterationStartOperation.java:72) > at org.infinispan.client.hotrod.impl.operations.IterationStartOperation.executeOperation(IterationStartOperation.java:21) > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56) > at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.startInternal(RemoteCloseableIterator.java:127) > at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.start(RemoteCloseableIterator.java:140) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.retrieveEntries(RemoteCacheImpl.java:162) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.retrieveEntries(RemoteCacheImpl.java:168) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.retrieveEntries(RemoteCacheImpl.java:173) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl$KeySet.iterator(RemoteCacheImpl.java:553) > at org.mposolda.ispn.InfinispanRemote.main(InfinispanRemote.java:34) > {code} > Indeed, When looking at this line of class RemoteCacheImpl, I see that it references the class, which seem that it was added in HotRodServer version 9. This looks like the cause of the error: https://github.com/infinispan/infinispan/blob/master/client/hotrod-client... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8719) KeySet.(iterator|spliterator|stream) not compatible with versions before 9.1

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8719?page=com.atlassian.jira.plugin.... ] William Burns reopened ISPN-8719: --------------------------------- > KeySet.(iterator|spliterator|stream) not compatible with versions before 9.1 > ---------------------------------------------------------------------------- > > Key: ISPN-8719 > URL: https://issues.jboss.org/browse/ISPN-8719 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.0.Final, 9.2.0.Final > Reporter: Marek Posolda > Assignee: William Burns > Priority: Critical > Fix For: 9.1.8.Final, 9.2.2.Final, 9.3.0.Alpha1 > > Attachments: InfinispanRemote.java > > > Steps to reproduce: > 1) Use infinispan server version 8.2.6 (or JDG server 7.1.0) and start it. > {code} > cd JDG_HOME/bin > ./standalone.sh > {code} > 2) Create sample java project having dependency on latest dependency 9.2.0.CR1 in pom.xml: > {code} > <dependencies> > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-core</artifactId> > <version>9.2.0.CR1</version> > </dependency> > <dependency> > <groupId>org.infinispan</groupId> > <artifactId>infinispan-cachestore-remote</artifactId> > <version>9.2.0.CR1</version> > </dependency> > </dependencies> > {code} > 3) Add one simple java class based on the tutorial: http://infinispan.org/tutorials/simple/remote/ . The only difference is that I use hotRod protocolVersion 2.5 and calling: > {code} > remoteCache.keySet().iterator().hasNext() > {code}. I am attaching the class in attachement. > 4) Run the class. Seeing exception in both server log and on client-side. > Server exception > {code} > 10:44:20,365 ERROR [org.infinispan.server.hotrod.CacheDecodeContext] (HotRodServerWorker-6-1) ISPN005003: Exception reported: java.lang.IllegalStateException: ISPN006016: Factory 'org.infinispan.server.hotrod.HotRodServer$ToEmptyBytesKeyValueFilterConverter' not found in server > at org.infinispan.server.hotrod.iteration.DefaultIterationManager.getFactory(DefaultIterationManager.java:148) > at org.infinispan.server.hotrod.iteration.DefaultIterationManager.start(DefaultIterationManager.java:131) > at org.infinispan.server.hotrod.ContextHandler.realRead(ContextHandler.java:175) > at org.infinispan.server.hotrod.ContextHandler.lambda$channelRead0$1(ContextHandler.java:57) > at org.infinispan.server.hotrod.ContextHandler$$Lambda$86/1492247987.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) > at java.lang.Thread.run(Thread.java:745) > {code} > Client exception: > {code} > Jan 24, 2018 10:44:20 AM org.infinispan.client.hotrod.impl.protocol.Codec20 checkForErrorsInResponseStatus > WARN: ISPN004005: Error received from the server: java.lang.IllegalStateException: ISPN006016: Factory 'org.infinispan.server.hotrod.HotRodServer$ToEmptyBytesKeyValueFilterConverter' not found in server > Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=5 returned server error (status=0x85): java.lang.IllegalStateException: ISPN006016: Factory 'org.infinispan.server.hotrod.HotRodServer$ToEmptyBytesKeyValueFilterConverter' not found in server > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:408) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:162) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:148) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) > at org.infinispan.client.hotrod.impl.operations.IterationStartOperation.executeOperation(IterationStartOperation.java:72) > at org.infinispan.client.hotrod.impl.operations.IterationStartOperation.executeOperation(IterationStartOperation.java:21) > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56) > at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.startInternal(RemoteCloseableIterator.java:127) > at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.start(RemoteCloseableIterator.java:140) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.retrieveEntries(RemoteCacheImpl.java:162) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.retrieveEntries(RemoteCacheImpl.java:168) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.retrieveEntries(RemoteCacheImpl.java:173) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl$KeySet.iterator(RemoteCacheImpl.java:553) > at org.mposolda.ispn.InfinispanRemote.main(InfinispanRemote.java:34) > {code} > Indeed, When looking at this line of class RemoteCacheImpl, I see that it references the class, which seem that it was added in HotRodServer version 9. This looks like the cause of the error: https://github.com/infinispan/infinispan/blob/master/client/hotrod-client... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2018