March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1098) Graph - Automate right panel

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1098: ------------------------------------- Summary: Graph - Automate right panel Key: SWSQE-1098 URL: https://issues.redhat.com/browse/SWSQE-1098 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Automate data shown and tabs based on the Graph object type selection. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1099) Automate labels https://github.com/kiali/kiali-ui/pull/1686

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1099: ------------------------------------- Summary: Automate labels https://github.com/kiali/kiali-ui/pull/1686 Key: SWSQE-1099 URL: https://issues.redhat.com/browse/SWSQE-1099 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2461) Clustering can fail when re-adding an existing node using TCP_NIO2

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2461?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2461: -------------------------------- You don't need to use {{use_ip_addrs}} to mark special nodes; this can be done via custom addresses \[1\]. Use for example {{ExtendedUUID}} or {{FlagsUUID}}. It would be nice if you could test this, so I know whether your issue is caused by {{use_ip_addrs}}, or not. \[1\] http://www.jgroups.org/manual4/index.html#CustomAddresses \[2\] http://www.jgroups.org/manual4/index.html#MembershipChangePolicy > Clustering can fail when re-adding an existing node using TCP_NIO2 > ------------------------------------------------------------------ > > Key: JGRP-2461 > URL: https://issues.redhat.com/browse/JGRP-2461 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.8 > Reporter: Robert Mitchell > Assignee: Bela Ban > Priority: Major > > When a node leaves a cluster and then later attempts to re-enter, a race condition can occur where the clustering fails to occur. Here is the sequence of events that seems to allow this to occur: > # The rejoining node must have a "higher" IP address than the current cluster coordinator. > # On the rejoin attempt, the coordinator sends a message to the rejoining node before the rejoining node sends to the coordinator using its prior address. I have seen this happen for two reasons: > ## UNICAST3 is resending messages (which often happens with the final LEAVE_RSP from the prior cluster membership because it apparently does not get acked before the connection closes) > ## TCPPING is sending a ping request to the cached prior address. > # The connection gets established. It will then be used by the rejoining node whenever communicating with the cluster coordinator. > # However, the cluster coordinator has this as the connection for the prior address. So the following happens whenever it wants to send a message to the rejoining node: > ## It will attempt to create a new connection. > ## The rejoining node will reject the connection as a redundant connection with its current connection taking precedence since it is coming from the same logical address as the "bad" connection. > Since the messages needed to find and join the cluster or merge the two clusters are all unicast messages, the rejoining node will never get them and not be able to join until something happens that causes the initial connection to get closed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4830) Add a Docker composer to connect BC and Kie Server images

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4830?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-4830: ------------------------------------------- Fix Version/s: 7.36.0.Final (was: 7.35.0.Final) > Add a Docker composer to connect BC and Kie Server images > --------------------------------------------------------- > > Key: DROOLS-4830 > URL: https://issues.redhat.com/browse/DROOLS-4830 > Project: Drools > Issue Type: Feature Request > Components: docker images > Affects Versions: 7.30.0.Final > Reporter: Ricardo Zanini Fernandes > Assignee: Ricardo Zanini Fernandes > Priority: Major > Fix For: 7.36.0.Final > > > It's natural to have BC and KIE servers working together. Would be nice to have a Docker composer file that fires up the two instances at once. This will support use cases such authoring on BC and deploying in the connected KIE Server. > References: https://www.drools.org/download/download.html -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3160) adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm)

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-3160?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-3160: ------------------------------------------- Fix Version/s: 7.36.0.Final (was: 7.35.0.Final) > adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm) > ------------------------------------------------------------ > > Key: DROOLS-3160 > URL: https://issues.redhat.com/browse/DROOLS-3160 > Project: Drools > Issue Type: Feature Request > Reporter: Michael Biarnes Kiefer > Assignee: Toni Rikkola > Priority: Major > Fix For: 7.36.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2254) Automate .proto files rebuild in pom.xml

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-2254?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-2254: ------------------------------------------- Fix Version/s: 7.36.0.Final (was: 7.35.0.Final) > Automate .proto files rebuild in pom.xml > ---------------------------------------- > > Key: DROOLS-2254 > URL: https://issues.redhat.com/browse/DROOLS-2254 > Project: Drools > Issue Type: Task > Components: tools > Affects Versions: 7.5.0.Final > Reporter: Dmitry Volodin > Assignee: Dmitry Volodin > Priority: Minor > Fix For: 7.36.0.Final > > > According to contribution guide, any .proto file or protobuf version changes it's necessary to download protoc utility and regenerate Java classes based on .proto files. > This will add automation for downloading protoc utility and Java classes generation based on Maven Protocol Buffers Plugin. There is no timestamps and other build related info inside generated Java files and no changes will be added on each new build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5095) [DMN Designer] Investigate performance switching between editor instances

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5095?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-5095: ------------------------------------------- Fix Version/s: 7.36.0.Final (was: 7.35.0.Final) > [DMN Designer] Investigate performance switching between editor instances > ------------------------------------------------------------------------- > > Key: DROOLS-5095 > URL: https://issues.redhat.com/browse/DROOLS-5095 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Fix For: 7.36.0.Final > > Attachments: switch-dmn.webm > > > This JIRA is to investigate the reported performance issue switching between different DMN Designer instances in Business Central. > The issue was noticed by [~jomarko] when testing DROOLS-5058 (although the fix therein should have had *zero* affect on switching). > For more details see the video [^switch-dmn.webm] > h2. Manual acceptance test > - Prepare 5 DMN models in project > - Open all in parallel > - Try to switch between them, keep all opened -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13176) Add jboss-ejb-client_1_3.xsd schema

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-13176?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty commented on WFLY-13176: -------------------------------------------- [~cfang] are you working on this ? > Add jboss-ejb-client_1_3.xsd schema > ------------------------------------ > > Key: WFLY-13176 > URL: https://issues.redhat.com/browse/WFLY-13176 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > > WildFly currently (2020-02-28) includes schemas 1.0, 1.1, 1.2, but not 1.3: > {code} > ./src/main/resources/schema/jboss-ejb-client_1_1.xsd > ./src/main/resources/schema/jboss-ejb-client_1_0.xsd > ./src/main/resources/schema/jboss-ejb-client_1_2.xsd > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5406) Update to add a testcase for the journal store setting in the transaction subsystem

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/WFLY-5406?page=com.atlassian.jira.plugin... ] Mayank Kunwar resolved WFLY-5406. --------------------------------- Resolution: Done > Update to add a testcase for the journal store setting in the transaction subsystem > ----------------------------------------------------------------------------------- > > Key: WFLY-5406 > URL: https://issues.redhat.com/browse/WFLY-5406 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite, Transactions > Reporter: Zheng Feng > Assignee: Mayank Kunwar > Priority: Minor > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5406) Update to add a testcase for the journal store setting in the transaction subsystem

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/WFLY-5406?page=com.atlassian.jira.plugin... ] Mayank Kunwar commented on WFLY-5406: ------------------------------------- The testcase is already added long back. Here is the link for committed changes : https://github.com/wildfly/wildfly/commit/0eb316f437b472f6b2cab2ad6f4666a... > Update to add a testcase for the journal store setting in the transaction subsystem > ----------------------------------------------------------------------------------- > > Key: WFLY-5406 > URL: https://issues.redhat.com/browse/WFLY-5406 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite, Transactions > Reporter: Zheng Feng > Assignee: Mayank Kunwar > Priority: Minor > -- 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