March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2106) Prepare for JDK 11

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2106?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2106: --------------------------- Affects Version/s: 5.0.0.Alpha3 Fix Version/s: (was: 5.0) > Prepare for JDK 11 > ------------------ > > Key: JGRP-2106 > URL: https://issues.redhat.com/browse/JGRP-2106 > Project: JGroups > Issue Type: Task > Affects Versions: 5.0.0.Alpha3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > > Investigate the changes needed to run with JDK 11. Probably module.info classes are all that's needed. > Other things to investigate: > * Replace {{Condition}} with {{Predicate}} > * Remove {{FORWARD_TO_COORD}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2405) Re-activate Channel

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2405?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2405: --------------------------- Affects Version/s: 5.0.0.Alpha3 Fix Version/s: (was: 5.0) > Re-activate Channel > ------------------- > > Key: JGRP-2405 > URL: https://issues.redhat.com/browse/JGRP-2405 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 5.0.0.Alpha3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > > The {{Channel}} interface has been deprecated. However, to implement JGraSS [1], we need it. Remove the @Deprecated tag and make JChannel implement Channel. > [1] https://issues.jboss.org/browse/JGRP-2411 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2403) Dump information in panic scenarios

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2403?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2403: --------------------------- Affects Version/s: 5.0.0.Alpha3 Fix Version/s: (was: 5.0) (was: 4.2.2) > Dump information in panic scenarios > ----------------------------------- > > Key: JGRP-2403 > URL: https://issues.redhat.com/browse/JGRP-2403 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 5.0.0.Alpha3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > > When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level. > Also dump the most important information to another log (file) periodically (e.g. every 15 minutes). This log should be enabled by default, e.g. in Infinispan. > These files can be sent to support via an SOS report. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2415) Fluent setters

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2415?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2415: --------------------------- Affects Version/s: 5.0.0.Alpha3 Fix Version/s: (was: 5.0) > Fluent setters > -------------- > > Key: JGRP-2415 > URL: https://issues.redhat.com/browse/JGRP-2415 > Project: JGroups > Issue Type: Task > Affects Versions: 5.0.0.Alpha3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > > Make all setters of protocols/other classes fluent, e.g. instead of returning {{void}}, make a setter return the class so that setter calls can be chained. > This breaks API compatibility, so it can only be done in 5.0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2430) GossipRouter: more efficient routing

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2430?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2430: --------------------------- Affects Version/s: 5.0.0.Alpha3 Fix Version/s: (was: 5.0) (was: 4.2.2) > GossipRouter: more efficient routing > ------------------------------------ > > Key: JGRP-2430 > URL: https://issues.redhat.com/browse/JGRP-2430 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 5.0.0.Alpha3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > > GossipRouter supports both NIO (ByteBuffer) and TCP (stream-based) connections. In both cases, however, the entire message is read and then routed to the destination address. > It would be better to only read the cluster name and target address, and then use efficient stream-to-stream (or channel-to-channel) _transfer mechanisms_, which avoids temporary copies of data and the full reading of messages. > Also look into routing of entire message _batches_. > Investigate whether this is possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2402) SOS report

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2402?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2402: --------------------------- Affects Version/s: 5.0.0.Alpha3 Fix Version/s: (was: 5.0) (was: 4.2.2) > SOS report > ---------- > > Key: JGRP-2402 > URL: https://issues.redhat.com/browse/JGRP-2402 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 5.0.0.Alpha3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > > Add the ability to dump the most important attributes to a file / log (configurable), e.g.: > * Max threads > * Number of rejected messages > * Size of retransmission tables (NAKACK2, UNICAST3) > This can be used to diagnose issues by telling the customer to invoke this command and attach the resulting file to a ticket -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2442) Performance tests

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2442?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2442: --------------------------- Affects Version/s: 5.0.0.Alpha3 Fix Version/s: (was: 5.0) > Performance tests > ----------------- > > Key: JGRP-2442 > URL: https://issues.redhat.com/browse/JGRP-2442 > Project: JGroups > Issue Type: Task > Affects Versions: 5.0.0.Alpha3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > > Run UPerf/MPerf before releasing 5.0.0.Final. > Performance should be slightly better due to reduced memory pressure (LongMessage, EmptyMessage, one less memory allocation)... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2412) GMS: reduce likelihood of merges on concurrent new member startup

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2412?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2412: --------------------------- Affects Version/s: 5.0.0.Alpha3 Fix Version/s: (was: 5.0) (was: 4.2.2) > GMS: reduce likelihood of merges on concurrent new member startup > ----------------------------------------------------------------- > > Key: JGRP-2412 > URL: https://issues.redhat.com/browse/JGRP-2412 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 5.0.0.Alpha3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > > When multiple new members are started concurrently, and no coord is present yet, different clients get different discovery results, and this may lead to merging. > If we have no coord, we could run the discovery protocol multiple time, *with the current members list being cached*, and then might end up with a more similar list of new members. > This could be governed by an additional attribute in {{Discovery}} ({{num_discovery_runs}}?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2304) ASYM_ENCRYPT: see if FragmentedMessages are handled correctly

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2304?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2304: --------------------------- Affects Version/s: 5.0.0.Alpha3 Fix Version/s: (was: 5.0) > ASYM_ENCRYPT: see if FragmentedMessages are handled correctly > ------------------------------------------------------------- > > Key: JGRP-2304 > URL: https://issues.redhat.com/browse/JGRP-2304 > Project: JGroups > Issue Type: Task > Affects Versions: 5.0.0.Alpha3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > > Check the following scenario: > * FRAG4 fragments a message into 4 FragmentedMessages > * Confirm that ASYM_ENCRYPT correctly encrypts only the fragments > Ditto for COMPRESS -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2374) TCP/TCP_NIO2: add TLS

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2374?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2374: --------------------------- Affects Version/s: 5.0.0.Alpha3 Fix Version/s: (was: 5.0) (was: 4.2.2) > TCP/TCP_NIO2: add TLS > --------------------- > > Key: JGRP-2374 > URL: https://issues.redhat.com/browse/JGRP-2374 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 5.0.0.Alpha3 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > > Add TLS to the TCP and TCP_NIO2 transports. Look into wildfly-openssl [1] for the impl. > [1] https://github.com/wildfly-security/wildfly-openssl -- 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

2008

2007

2006

jboss-jira March 2020