September 2018 - infinispan-issues

[JBoss JIRA] (ISPN-7057) Refactor StatsChannelHandler to support null transport

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7057?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7057: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Refactor StatsChannelHandler to support null transport > ------------------------------------------------------ > > Key: ISPN-7057 > URL: https://issues.jboss.org/browse/ISPN-7057 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Sebastian Łaskawiec > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7590) Invocation idempotence

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7590?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7590: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Invocation idempotence > ---------------------- > > Key: ISPN-7590 > URL: https://issues.jboss.org/browse/ISPN-7590 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.CR2 > Reporter: Radim Vansa > Assignee: Radim Vansa > Labels: consistency > Fix For: 9.4.0.Final > > > This is an umbrella JIRA to change the way how we deal with retries after topology change. > Please link any outstanding issues that refer to incorrect return values of command during topology change. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7470) Distributed executor does not fail over unless future.get() is called

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7470?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7470: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Distributed executor does not fail over unless future.get() is called > --------------------------------------------------------------------- > > Key: ISPN-7470 > URL: https://issues.jboss.org/browse/ISPN-7470 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.6.Final, 9.0.0.CR1 > Reporter: Dan Berindei > Assignee: William Burns > Fix For: 9.4.0.Final > > > After ISPN-6392, {{DistributedExecutorService.submit(...)}} nominally returns a {{CompletableFuture}}. However, it doesn't behave like a regular {{CompletableFuture}}, because it doesn't run the failure policy until the user calls {{future.get()}}. > {{future.isComplete()}} will return {{true}} before running the failure policy, and {{future.whenComplete(callback)}} will also execute the callback before running the failure policy. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7415) Immortal entries use EmbeddedExpirableMetadata instead of EmbeddedMetadata

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7415?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7415: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Immortal entries use EmbeddedExpirableMetadata instead of EmbeddedMetadata > -------------------------------------------------------------------------- > > Key: ISPN-7415 > URL: https://issues.jboss.org/browse/ISPN-7415 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.4.0.Final > > > The default lifespan and maxIdle are -1 to signal no expiration, but calling {{EmbeddedMetadata.Builder.lifespan\(x)}} with any value will make it create an {{EmbeddedExpirableMetadata}} instance. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7407) Investigate flow control performance

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7407?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7407: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Investigate flow control performance > ------------------------------------ > > Key: ISPN-7407 > URL: https://issues.jboss.org/browse/ISPN-7407 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7401) AbstractProtocolServer relying on startDefaultCache

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7401?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7401: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > AbstractProtocolServer relying on startDefaultCache > --------------------------------------------------- > > Key: ISPN-7401 > URL: https://issues.jboss.org/browse/ISPN-7401 > Project: Infinispan > Issue Type: Task > Components: Server > Reporter: Sanne Grinovero > Assignee: Tristan Tarrant > Fix For: 9.4.0.Final > > > The {{AbstractProtocolServer}} class is used/extended by various other tools, including testing infrastructure of OGM. > It currently is "booting" the system by starting the default cache. This concept needs an update. > See {{org.infinispan.server.core.AbstractProtocolServer.startDefaultCache()}} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7337) Enable configuring near cache via properties

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7337?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7337: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Enable configuring near cache via properties > -------------------------------------------- > > Key: ISPN-7337 > URL: https://issues.jboss.org/browse/ISPN-7337 > Project: Infinispan > Issue Type: Bug > Components: JCache, Remote Protocols > Affects Versions: 8.2.5.Final, 9.0.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.4.0.Final > > > So that near cache can be enabled with Hot Rod client when used via JCache interface. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7654) Ickle parser should have a different representation for each literal type instead of using string for everything

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7654?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7654: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Ickle parser should have a different representation for each literal type instead of using string for everything > ---------------------------------------------------------------------------------------------------------------- > > Key: ISPN-7654 > URL: https://issues.jboss.org/browse/ISPN-7654 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > > All constant literals regardless of type are represented as string now and are later parsed into integers, booleans, etc, when the query is translated. We should do this at the beginning phase of parsing. See ConstantLiteralTree class. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7643) Coordinator status is unavailable in Infinispan cluster

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7643?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7643: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > Coordinator status is unavailable in Infinispan cluster > ------------------------------------------------------- > > Key: ISPN-7643 > URL: https://issues.jboss.org/browse/ISPN-7643 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Sebastian Łaskawiec > Fix For: 9.4.0.Final > > > It seems that Coordinator field uses JGroups Address class which can be displayed properly. Since we already have a Coordinator Address field, maybe the best way would be to remove this from JMX. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7634) SerializationConfiguration.advancedExternalizers() map should not be mutable

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7634?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7634: ---------------------------------- Fix Version/s: 9.4.0.Final (was: 9.4.0.CR3) > SerializationConfiguration.advancedExternalizers() map should not be mutable > ---------------------------------------------------------------------------- > > Key: ISPN-7634 > URL: https://issues.jboss.org/browse/ISPN-7634 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.4.0.Final > > > Currently {{SerializationConfiguration.advancedExternalizers()}} returns a mutable {{HashMap}}. We only read it once on startup, so modifying it won't break anything, but it should be immutable to make it clear that externalizers cannot be added at runtime. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2018