February 2020 - infinispan-issues

[JBoss JIRA] (ISPN-11127) Protocol servers don't pre-start caches when transport is disabled

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11127?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11127: ----------------------------------- Fix Version/s: 10.1.4.Final (was: 10.1.3.Final) > Protocol servers don't pre-start caches when transport is disabled > ------------------------------------------------------------------ > > Key: ISPN-11127 > URL: https://issues.redhat.com/browse/ISPN-11127 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.4.Final > > > The various protocol servers have different initialization steps to ensures that caches are pre-started which don't work in all cases. In particular the REST server doesn't pre-start caches and the Hot Rod server pre-starts only if the transport is enabled. > This should be handled uniformly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11126) Health check fails when authz is enabled and cache is not yet started

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11126?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11126: ----------------------------------- Fix Version/s: 10.1.4.Final (was: 10.1.3.Final) > Health check fails when authz is enabled and cache is not yet started > --------------------------------------------------------------------- > > Key: ISPN-11126 > URL: https://issues.redhat.com/browse/ISPN-11126 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, REST > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.4.Final > > > When using predefined caches on a container with authorization, and the caches have not been started, the health handler for the cachemanager resource fails with an authorization error. > The call should be wrapped in a SecurityAction. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11113) ScatteredDelayedAvailabilityUpdateTest takes too long

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11113?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11113: ----------------------------------- Fix Version/s: 10.1.4.Final (was: 10.1.3.Final) > ScatteredDelayedAvailabilityUpdateTest takes too long > ----------------------------------------------------- > > Key: ISPN-11113 > URL: https://issues.redhat.com/browse/ISPN-11113 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 10.1.4.Final, 11.0.0.Final > > > Partition handling tests use {{LOCAL_PING.setClusterName()}} with a unique name to disable discovery, otherwise partitions would try to merge while they are supposed to stay separate. > But {{LOCAL_PING}} uses the cluster name on stop to remove the node from the static discovery map. If the test doesn't change the cluster name back, {{LOCAL_PING}} doesn't remove the node, the next test method sees an existing coordinator, and tries to connect to it. When a test has lots of test methods, like {{ScatteredDelayedAvailabilityUpdateTest}}, each test method leaves one more coordinator in the discovery map, and each test method takes longer to start the first method. > {noformat} > 09:08:52,758 DEBUG (testng:[]) [GMS] address=NodeA-30899, cluster=org.infinispan.partitionhandling.ScatteredDelayedAvailabilityUpdateTest[SCATTERED_SYNC, bias=NEVER, DENY_READ_WRITES], physical address=127.0.0.1:51941 > 09:08:52,774 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:08:52,774 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:08:52,774 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-5606 > 09:08:54,774 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-5606 timed out (after 2000 ms), on try 0 > 09:08:54,774 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-64297 > 09:08:56,775 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-64297 timed out (after 2000 ms), on try 0 > 09:08:56,775 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-48475 > 09:08:58,775 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-48475 timed out (after 2000 ms), on try 0 > 09:08:58,775 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-17288 > 09:09:00,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-17288 timed out (after 2000 ms), on try 0 > 09:09:00,776 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-2608 > 09:09:02,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-2608 timed out (after 2000 ms), on try 0 > 09:09:02,776 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:09:02,776 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:09:02,776 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-5606 > 09:09:04,776 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-5606 timed out (after 2000 ms), on try 1 > ... > 09:09:12,777 TRACE (testng:[]) [GMS] NodeA-30899: discovery took 0 ms, members: 21 rsps (5 coords) [done] > 09:09:12,778 DEBUG (testng:[]) [GMS] NodeA-30899: found multiple coords: [NodeA-2608, NodeA-5606, NodeA-17288, NodeA-64297, NodeA-48475] > 09:09:12,778 DEBUG (testng:[]) [GMS] NodeA-30899: sending JOIN(NodeA-30899) to NodeA-2608 > 09:09:14,778 WARN (testng:[]) [GMS] NodeA-30899: JOIN(NodeA-30899) sent to NodeA-2608 timed out (after 2000 ms), on try 2 > ... > 09:09:22,780 WARN (testng:[]) [GMS] NodeA-30899: too many JOIN attempts (3): becoming singleton > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11377) Change default flow control protocol back to UFC/MFC

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11377?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11377: ----------------------------------- Fix Version/s: 10.1.4.Final (was: 10.1.3.Final) > Change default flow control protocol back to UFC/MFC > ---------------------------------------------------- > > Key: ISPN-11377 > URL: https://issues.redhat.com/browse/ISPN-11377 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 9.4.18.Final, 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Alpha2 > > > The server default configuration started using {{UFC_NB}} and {{MFC_NB}} in order to avoid blocking on the Netty event loop threads, slowing client requests, and then the core default configurations started using {{UFC_NB}} and {{MFC_NB}} as well with ISPN-9886. > Unfortunately the _NB variants aren't really non-blocking: they have an extra queue for messages that require more credits, but that queue is limited (2MB by default), and once the queue is full, they also block. They also have much more complex locking than the blocking variants: we actually had to increase max_credits from 2MB to 3MB in order to get the same performance with {{UFC_NB}} that we had with {{UFC}}. > We're changing the defaults back to {{UFC}} and {{MFC}} while we investigate possible alternatives to avoid blocking. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11226) TaskContext doesn't contain cache manager in distributed server task

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11226?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11226: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TaskContext doesn't contain cache manager in distributed server task > -------------------------------------------------------------------- > > Key: ISPN-11226 > URL: https://issues.redhat.com/browse/ISPN-11226 > Project: Infinispan > Issue Type: Bug > Components: Server, Tasks > Affects Versions: 9.4.17.Final, 10.1.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.3.Final, 11.0.0.Alpha2, 9.4.19.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11302) There is no context-initializers in the javadoc for Hot Rod client configuration.

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11302?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11302: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > There is no context-initializers in the javadoc for Hot Rod client configuration. > --------------------------------------------------------------------------------- > > Key: ISPN-11302 > URL: https://issues.redhat.com/browse/ISPN-11302 > Project: Infinispan > Issue Type: Patch > Components: Hot Rod > Affects Versions: 10.0.1.Final, 10.1.1.Final > Reporter: Ippei Matsushima > Priority: Trivial > Fix For: 10.1.3.Final, 11.0.0.Alpha2 > > > Infinispan 10.0 seems to add a property called "infinispan.client.hotrod.context-initializers" to hotrod-client.properties, but there is no context-initializers in the javadoc of Hot Rod client configuration. > [Marshalling data|https://infinispan.org/docs/10.1.x/titles/hotrod_java/hotrod_java.ht...] > [Hot Rod client configuration API.|https://docs.jboss.org/infinispan/10.1/apidocs/org/infinispan/client...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11302) There is no context-initializers in the javadoc for Hot Rod client configuration.

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11302?page=com.atlassian.jira.plugi... ] Tristan Tarrant reassigned ISPN-11302: -------------------------------------- Assignee: Tristan Tarrant > There is no context-initializers in the javadoc for Hot Rod client configuration. > --------------------------------------------------------------------------------- > > Key: ISPN-11302 > URL: https://issues.redhat.com/browse/ISPN-11302 > Project: Infinispan > Issue Type: Patch > Components: Hot Rod > Affects Versions: 10.0.1.Final, 10.1.1.Final > Reporter: Ippei Matsushima > Assignee: Tristan Tarrant > Priority: Trivial > Fix For: 10.1.3.Final, 11.0.0.Alpha2 > > > Infinispan 10.0 seems to add a property called "infinispan.client.hotrod.context-initializers" to hotrod-client.properties, but there is no context-initializers in the javadoc of Hot Rod client configuration. > [Marshalling data|https://infinispan.org/docs/10.1.x/titles/hotrod_java/hotrod_java.ht...] > [Hot Rod client configuration API.|https://docs.jboss.org/infinispan/10.1/apidocs/org/infinispan/client...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11342) Use UserTool in server tests to generate users/groups property files

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11342?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11342: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use UserTool in server tests to generate users/groups property files > -------------------------------------------------------------------- > > Key: ISPN-11342 > URL: https://issues.redhat.com/browse/ISPN-11342 > Project: Infinispan > Issue Type: Bug > Components: Security, Server > Affects Versions: 10.1.2.Final, 11.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.3.Final, 11.0.0.Alpha2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11375) Numbers formatting

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11375?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11375: ----------------------------------- Fix Version/s: 10.1.4.Final (was: 10.1.3.Final) > Numbers formatting > ------------------- > > Key: ISPN-11375 > URL: https://issues.redhat.com/browse/ISPN-11375 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 4.0.0.Final, 10.1.2.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console > Fix For: 10.1.4.Final > > > Formatting of numbers must be according on stats display -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11375) Numbers formatting

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11375?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11375: ----------------------------------- Fix Version/s: 10.1.3.Final (was: 0.4.Final) > Numbers formatting > ------------------- > > Key: ISPN-11375 > URL: https://issues.redhat.com/browse/ISPN-11375 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 4.0.0.Final, 10.1.2.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console > Fix For: 10.1.3.Final > > > Formatting of numbers must be according on stats display -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2020