March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13236) Upgrade JGroups to 4.2.1.Final

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13236?page=com.atlassian.jira.plugi... ] Paul Ferraro closed WFLY-13236. ------------------------------- Resolution: Duplicate Issue Duplicate of WFLY-13235. > Upgrade JGroups to 4.2.1.Final > ------------------------------ > > Key: WFLY-13236 > URL: https://issues.redhat.com/browse/WFLY-13236 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Beta3 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > https://issues.redhat.com/projects/JGRP/versions/12344963 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

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: --------------------------- Summary: GMS: reduce likelihood of merges on concurrent new member startup (was: GMS: reduce likelyhood of merges on concurrent new member startup) > 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 > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0, 4.2.2 > > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13237) Investigate mod_cluster contexts appear 'enabled' in undertow proxy even without ENABLE-APP message

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13237: ------------------------------------- Summary: Investigate mod_cluster contexts appear 'enabled' in undertow proxy even without ENABLE-APP message Key: WFLY-13237 URL: https://issues.redhat.com/browse/WFLY-13237 Project: WildFly Issue Type: Bug Components: mod_cluster Reporter: Radoslav Husar Assignee: Radoslav Husar See https://github.com/wildfly/wildfly/pull/12974#pullrequestreview-372617078 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13121) jgroups channel protocol read-resource error with include-runtime

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13121?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13121: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13044, https://github.com/wildfly/wildfly/pull/13111 (was: https://github.com/wildfly/wildfly/pull/13044) > jgroups channel protocol read-resource error with include-runtime > ------------------------------------------------------------------ > > Key: WFLY-13121 > URL: https://issues.redhat.com/browse/WFLY-13121 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 19.0.0.Beta2 > Reporter: Jean Francois Denise > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > Start standlone-ha.xml > /subsystem=jgroups/channel=ee/protocol=UDP:read-resource(include-runtime > Client: > { > "outcome" => "failed", > "rolled-back" => true > } > Server: > 12:01:32,541 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("read-attribute") failed - address: ([ > ("subsystem" => "jgroups"), > ("channel" => "ee"), > ("protocol" => "UDP") > ]) - failure description: "newValue is null" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5160) DMN DT Analysis benchmark

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5160?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5160: ---------------------------------------- Example of param=7 full hypercube of 7 dimensions, complete, with no gaps/no overlaps !screenshot-1.png|thumbnail! > DMN DT Analysis benchmark > ------------------------- > > Key: DROOLS-5160 > URL: https://issues.redhat.com/browse/DROOLS-5160 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png > > > Given a parameter "param" > * DMN with param=9 means > * 9 InputData > * decision table of 512 rows. > * Will perform the full analysis of the hypercube of 9 dimensions, complete, with no gaps and overlaps > Result of full analysis no gaps no overlaps, U policy is: DMN: Decision Table Analysis of table 'decision' finished with no messages to be reported. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5160) DMN DT Analysis benchmark

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5160?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5160: ----------------------------------- Attachment: screenshot-1.png > DMN DT Analysis benchmark > ------------------------- > > Key: DROOLS-5160 > URL: https://issues.redhat.com/browse/DROOLS-5160 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png > > > Given a parameter "param" > * DMN with param=9 means > * 9 InputData > * decision table of 512 rows. > * Will perform the full analysis of the hypercube of 9 dimensions, complete, with no gaps and overlaps > Result of full analysis no gaps no overlaps, U policy is: DMN: Decision Table Analysis of table 'decision' finished with no messages to be reported. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5160) DMN DT Analysis benchmark

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5160: -------------------------------------- Summary: DMN DT Analysis benchmark Key: DROOLS-5160 URL: https://issues.redhat.com/browse/DROOLS-5160 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Given a parameter "param" * DMN with param=9 means * 9 InputData * decision table of 512 rows. * Will perform the full analysis of the hypercube of 9 dimensions, complete, with no gaps and overlaps Result of full analysis no gaps no overlaps, U policy is: DMN: Decision Table Analysis of table 'decision' finished with no messages to be reported. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13235) Upgrade JGroups to 4.2.1.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13235?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13235: ---------------------------------- Description: Changelog https://issues.redhat.com/projects/JGRP/versions/12344963 https://github.com/belaban/JGroups/releases/tag/JGroups-4.2.1.Final was: Changelog https://issues.redhat.com/projects/JGRP/versions/12344963 > Upgrade JGroups to 4.2.1.Final > ------------------------------ > > Key: WFLY-13235 > URL: https://issues.redhat.com/browse/WFLY-13235 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > Changelog > https://issues.redhat.com/projects/JGRP/versions/12344963 > https://github.com/belaban/JGroups/releases/tag/JGroups-4.2.1.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13235) Upgrade JGroups to 4.2.1.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13235?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13235: ---------------------------------- Fix Version/s: 20.0.0.Beta1 > Upgrade JGroups to 4.2.1.Final > ------------------------------ > > Key: WFLY-13235 > URL: https://issues.redhat.com/browse/WFLY-13235 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Beta1 > > > Changelog > https://issues.redhat.com/projects/JGRP/versions/12344963 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13236) Upgrade JGroups to 4.2.1.Final

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13236: ----------------------------------- Summary: Upgrade JGroups to 4.2.1.Final Key: WFLY-13236 URL: https://issues.redhat.com/browse/WFLY-13236 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 19.0.0.Beta3 Reporter: Paul Ferraro Assignee: Paul Ferraro https://issues.redhat.com/projects/JGRP/versions/12344963 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

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