December 2020 - infinispan-issues

[Red Hat JIRA] (ISPN-12448) Docs: Server getting started and cluster transport config

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-12448?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-12448: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8876, https://github.com/infinispan/infinispan/pull/8904 (was: https://github.com/infinispan/infinispan/pull/8876) > Docs: Server getting started and cluster transport config > --------------------------------------------------------- > > Key: ISPN-12448 > URL: https://issues.redhat.com/browse/ISPN-12448 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 12.0.0.Final > > > Improve server getting started to extend with next steps for using JGroups system properties to start building out cluster transport. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[Red Hat JIRA] (ISPN-12549) Fix missing Shrinkwrap dependencies in Server JUnit modules

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-12549: -------------------------------------- Summary: Fix missing Shrinkwrap dependencies in Server JUnit modules Key: ISPN-12549 URL: https://issues.redhat.com/browse/ISPN-12549 Project: Infinispan Issue Type: Enhancement Reporter: Tristan Tarrant On CI, the PMD plugin is causing java.lang.NoClassDefFoundError: [Lorg/jboss/shrinkwrap/api/spec/JavaArchive; in CI This is because the Server JUnit module dependencies on Shrinkwrap are not correct. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[Red Hat JIRA] (ISPN-12500) Possibility to separate the subdirectories under server-root

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12500?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12500: ----------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8882, https://github.com/infinispan/infinispan/pull/8903 (was: https://github.com/infinispan/infinispan/pull/8882) > Possibility to separate the subdirectories under server-root > ------------------------------------------------------------ > > Key: ISPN-12500 > URL: https://issues.redhat.com/browse/ISPN-12500 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 11.0.5.Final, 12.0.0.Dev06 > Reporter: Wolf-Dieter Fink > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.CR1, 11.0.8.Final > > > For administration purpose it should be possible to set different locations for server/conf server/data server/lib and server/log instead of keeping all together with server-root setting. > Additionally the lib directory should be scanned recursively, resolving symlinks and supporting bare files (e.g. property files) as well as Jar files. It should also be possible to specify multiple lib directories. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[Red Hat JIRA] (ISPN-12531) Support JGroups fix start port and port offset in the server for FD_SOCK

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12531?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12531: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8902 > Support JGroups fix start port and port offset in the server for FD_SOCK > ------------------------------------------------------------------------ > > Key: ISPN-12531 > URL: https://issues.redhat.com/browse/ISPN-12531 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 11.0.5.Final, 12.0.0.Dev06 > Reporter: Wolf-Dieter Fink > Assignee: Tristan Tarrant > Priority: Minor > > As the server parameter '-o' can add a port offset to the jgroups.bind.port the FD_SOCK port is not affected. Also the port is configured as random which is not ideal. > The legacy server used the socket-bindings to use a fixed start port (udp-fd=54200 and tcp-fd=57800) and incremented the port if the port-offset was used. > This should be similar for the new jgroups configuration. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[Red Hat JIRA] (ISPN-12531) Support JGroups fix start port and port offset in the server for FD_SOCK

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12531?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12531: ----------------------------------- Fix Version/s: 12.0.0.CR1 > Support JGroups fix start port and port offset in the server for FD_SOCK > ------------------------------------------------------------------------ > > Key: ISPN-12531 > URL: https://issues.redhat.com/browse/ISPN-12531 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 11.0.5.Final, 12.0.0.Dev06 > Reporter: Wolf-Dieter Fink > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 12.0.0.CR1 > > > As the server parameter '-o' can add a port offset to the jgroups.bind.port the FD_SOCK port is not affected. Also the port is configured as random which is not ideal. > The legacy server used the socket-bindings to use a fixed start port (udp-fd=54200 and tcp-fd=57800) and incremented the port if the port-offset was used. > This should be similar for the new jgroups configuration. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[Red Hat JIRA] (ISPN-12531) Support JGroups fix start port and port offset in the server for FD_SOCK

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12531?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12531: ----------------------------------- Status: Open (was: New) > Support JGroups fix start port and port offset in the server for FD_SOCK > ------------------------------------------------------------------------ > > Key: ISPN-12531 > URL: https://issues.redhat.com/browse/ISPN-12531 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 11.0.5.Final, 12.0.0.Dev06 > Reporter: Wolf-Dieter Fink > Priority: Minor > > As the server parameter '-o' can add a port offset to the jgroups.bind.port the FD_SOCK port is not affected. Also the port is configured as random which is not ideal. > The legacy server used the socket-bindings to use a fixed start port (udp-fd=54200 and tcp-fd=57800) and incremented the port if the port-offset was used. > This should be similar for the new jgroups configuration. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[Red Hat JIRA] (ISPN-12531) Support JGroups fix start port and port offset in the server for FD_SOCK

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12531?page=com.atlassian.jira.plugi... ] Tristan Tarrant reassigned ISPN-12531: -------------------------------------- Assignee: Tristan Tarrant > Support JGroups fix start port and port offset in the server for FD_SOCK > ------------------------------------------------------------------------ > > Key: ISPN-12531 > URL: https://issues.redhat.com/browse/ISPN-12531 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 11.0.5.Final, 12.0.0.Dev06 > Reporter: Wolf-Dieter Fink > Assignee: Tristan Tarrant > Priority: Minor > > As the server parameter '-o' can add a port offset to the jgroups.bind.port the FD_SOCK port is not affected. Also the port is configured as random which is not ideal. > The legacy server used the socket-bindings to use a fixed start port (udp-fd=54200 and tcp-fd=57800) and incremented the port if the port-offset was used. > This should be similar for the new jgroups configuration. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[Red Hat JIRA] (ISPN-12541) Remove ControlledRpcManager allRequests

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12541?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12541: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove ControlledRpcManager allRequests > --------------------------------------- > > Key: ISPN-12541 > URL: https://issues.redhat.com/browse/ISPN-12541 > Project: Infinispan > Issue Type: Task > Components: Test Suite > Affects Versions: 12.0.0.Dev07 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Trivial > Fix For: 12.0.0.CR1 > > > {{ControlledRpcManager.allRequests}} is not very useful for debugging, and because it's never used it only creates confusion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[Red Hat JIRA] (ISPN-12542) Do not allow stacking ControlledRpcManager

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12542?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12542: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Do not allow stacking ControlledRpcManager > ------------------------------------------ > > Key: ISPN-12542 > URL: https://issues.redhat.com/browse/ISPN-12542 > Project: Infinispan > Issue Type: Task > Components: Test Suite > Affects Versions: 12.0.0.Dev07 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Trivial > Fix For: 12.0.0.CR1 > > > Wrapping the same RpcManager twice is usually a mistake, e.g. copy-pasting without changing the cache index. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2020