February 2020 - jboss-jira - Jboss List Archives

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2402?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2402: --------------------------- Fix Version/s: 5.0 4.2.1 (was: 4.2.0) > SOS report > ---------- > > Key: JGRP-2402 > URL: https://issues.redhat.com/browse/JGRP-2402 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.1 > > > 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)

4 years, 3 months

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: --------------------------- Fix Version/s: 5.0 4.2.1 (was: 4.2.0) > Dump information in panic scenarios > ----------------------------------- > > Key: JGRP-2403 > URL: https://issues.redhat.com/browse/JGRP-2403 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.1 > > > When there is a panic situation (e.g. thread pool exhausted), dump information 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)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2401) Version number for configuration

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2401?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2401: --------------------------- Fix Version/s: 5.0 4.2.1 (was: 4.2.0) > Version number for configuration > -------------------------------- > > Key: JGRP-2401 > URL: https://issues.redhat.com/browse/JGRP-2401 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.1 > > > Add a version to the config, which corresponds with the JGroups version. > At startup, if the JGroups version and the confi version don't match, issue a warning. Possibly don't start if the major version differs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2406) MERGE3 not working with TCP using ForkJoinPool

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2406?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2406: --------------------------- Fix Version/s: 5.0 4.2.1 (was: 4.2.0) > MERGE3 not working with TCP using ForkJoinPool > ---------------------------------------------- > > Key: JGRP-2406 > URL: https://issues.redhat.com/browse/JGRP-2406 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.8 > Reporter: Olivier Peyrusse > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.1 > > Attachments: logs.tgz, project.zip, timeline.txt > > > With JDK11, using the TCP protocol with the ForkJoinPool is causing constant failures of MERGE3. > I consistently observed the following, from the point of view of a member M > - M asks for other coordinator views. It contacts A and B > - A and B send their views > - M waits and timeouts for receiving views and abort the merge > - immediately after aborting the merge, M process messages containing the views of A and B. > In [^timeline.txt], you will see the extracts for logs from the various members at play. > After many experiments, the one parameter causing this issue is in the TCP protocol. > {code:xml} > <TCP > ... > thread_pool.use_fork_join_pool="true" /> > {code} > Setting {{thread_pool.use_fork_join_pool}} to true repeatedly produces the problem, while using {{thread_pool.use_fork_join_pool}} with false works fine. > Project details: > - as tested within Kubernetes, this project uses KUBE_PING as its discovery protocol > - to understand the reason for the failed merges, I created the protocol MERGE4, that is MERGE3 with additional logs. > - [^logs.tgz] contains all logs from the various members involved in the test. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2410) TestNG: upgrade to 7.0.0

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2410?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2410: --------------------------- Fix Version/s: 5.0 4.2.1 (was: 4.2.0) > TestNG: upgrade to 7.0.0 > ------------------------ > > Key: JGRP-2410 > URL: https://issues.redhat.com/browse/JGRP-2410 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Optional > Fix For: 5.0, 4.2.1 > > > There were some issues running the stack-dependent tests in 7.0.0, that's why I reverted to 6.14.3. Need to revisit this. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

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: --------------------------- Fix Version/s: 5.0 4.2.1 (was: 4.2.0) > GossipRouter: more efficient routing > ------------------------------------ > > Key: JGRP-2430 > URL: https://issues.redhat.com/browse/JGRP-2430 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0, 4.2.1 > > > 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)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2450) Enable fibers / project Loom

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2450?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2450. ---------------------------- Resolution: Done > Enable fibers / project Loom > ---------------------------- > > Key: JGRP-2450 > URL: https://issues.redhat.com/browse/JGRP-2450 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0, 4.2.0 > > > Add {{use_fibers}} to {{TP}}. > When enabled, we use reflection to create fibers rather than threads in {{DefaultThreadFactory}}. > This requires Java 15/Loom. If not found, regular threads are returned instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13142) Can't create a Connection Factory using JGroups discovery

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13142?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13142: ---------------------------------- Summary: Can't create a Connection Factory using JGroups discovery (was: Can't create a Connection Factory using Jgroups discovery) > Can't create a Connection Factory using JGroups discovery > --------------------------------------------------------- > > Key: WFLY-13142 > URL: https://issues.redhat.com/browse/WFLY-13142 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 19.0.0.Beta2 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Critical > > When trying to configure a connection factory with a JGroup Discovery Group it fails with the exception: > { > "outcome" => "failed", > "failure-description" => { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.messaging-activemq.bindings.discovery.dg-group1"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging-activemq.jms.pooled-connection-factory.activemq-ra is missing [jboss.messaging-activemq.bindings.discovery.dg-group1]"] > }, > "rolled-back" => true > } -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2450) Enable fibers / project Loom

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2450?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2450: --------------------------- Fix Version/s: 4.2.0 > Enable fibers / project Loom > ---------------------------- > > Key: JGRP-2450 > URL: https://issues.redhat.com/browse/JGRP-2450 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0, 4.2.0 > > > Add {{use_fibers}} to {{TP}}. > When enabled, we use reflection to create fibers rather than threads in {{DefaultThreadFactory}}. > This requires Java 15/Loom. If not found, regular threads are returned instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2450) Enable fibers / project Loom

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2450?page=com.atlassian.jira.plugin... ] Bela Ban reopened JGRP-2450: ---------------------------- Add backport to 4.2.0 > Enable fibers / project Loom > ---------------------------- > > Key: JGRP-2450 > URL: https://issues.redhat.com/browse/JGRP-2450 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > Add {{use_fibers}} to {{TP}}. > When enabled, we use reflection to create fibers rather than threads in {{DefaultThreadFactory}}. > This requires Java 15/Loom. If not found, regular threads are returned instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2020