March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4882) Broken 'domain.xml' after migration of <host-scoped-roles> leading to 'Boostrap error' in HAL

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFCORE-4882?page=com.atlassian.jira.plug... ] Chao Wang updated WFCORE-4882: ------------------------------ Summary: Broken 'domain.xml' after migration of <host-scoped-roles> leading to 'Boostrap error' in HAL (was: [GSS](7.2.z) CMTOOL-255 - Broken 'domain.xml' after migration of <host-scoped-roles> leading to 'Boostrap error' in HAL) > Broken 'domain.xml' after migration of <host-scoped-roles> leading to 'Boostrap error' in HAL > --------------------------------------------------------------------------------------------- > > Key: WFCORE-4882 > URL: https://issues.redhat.com/browse/WFCORE-4882 > Project: WildFly Core > Issue Type: Bug > Components: Management, Server > Affects Versions: 11.0.0.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Major > > When migrating a domain configuration from JBoss EAP 7.1.6 having a broken {{<host-scoped-roles>}} configuration, the resulting {{domain.xml}} on EAP 7.2 is broken as well. > JBoss EAP 7.1 is relaxed during accessing the HAL and simply ignores the broken configuration, whereas JBoss EAP 7.2 will not allow access to the HAL and report a *_Bootstrap error_*. > The {{jboss-server-migration.[sh|bat]}} should identify this broken configuration and *deny* the migration of it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5006) [DMN Designer] Code Completion - When users leave it opened, it never disappears

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-5006?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-5006: ------------------------------------ Sprint: 2020 Week 10-12 (from Mar 2) > [DMN Designer] Code Completion - When users leave it opened, it never disappears > -------------------------------------------------------------------------------- > > Key: DROOLS-5006 > URL: https://issues.redhat.com/browse/DROOLS-5006 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: 2020-02-04 15.34.09.gif > > > When users leave it opened, it never disappears. > *Steps to reproduce:* > !2020-02-04 15.34.09.gif|width=800! -- 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 Robert Mitchell (Jira)

[ https://issues.redhat.com/browse/JGRP-2461?page=com.atlassian.jira.plugin... ] Robert Mitchell commented on JGRP-2461: --------------------------------------- We do rely on the use_ip_addrs, mostly because we want to know if certain "special" nodes are in the cluster. We could probably do that in other ways, but because the IP addresses of these nodes are well known throughout the cluster it was easiest to do that way. I had wondered whether it was part of the problem or not, but have not been able to find time to investigate. Given that, I think it could still happen. The problem is that the connection being made from the cluster coordinator is tied to the old logical address of the node and the node won't let it make a second connection which uses the new logical address. I think TCPPING would not cause problems without this setting because it's use of the IpAddressUUID as a PhysicalAddress is closely tied to the issue. However, for UNICAST3, I would think its need to send the unacknowledged message to the logical address would still tie the connection to the old logical address even if use_ip_addrs were not set. > 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] (WFLY-13261) Messages are being added to topic even if there are no subscribers

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13261?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet updated WFLY-13261: ------------------------------------- Fix Version/s: 19.0.1.Final 20.0.0.Beta1 > Messages are being added to topic even if there are no subscribers > ------------------------------------------------------------------- > > Key: WFLY-13261 > URL: https://issues.redhat.com/browse/WFLY-13261 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 19.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > Fix For: 19.0.1.Final, 20.0.0.Beta1 > > > After applying EAP 7.2 Update 7 , messages seem to be added to a topic even when there are no subscribers on the topic. > When subscribers are attached to a topic they seem to consume messages from a topic but the messages is not removed from the underlying physical queue resulting in the destination growing indefinitely in size. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13261) Messages are being added to topic even if there are no subscribers

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13261?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet updated WFLY-13261: ------------------------------------- Summary: Messages are being added to topic even if there are no subscribers (was: [GSS](7.2.z) Messages are being added to topic even if there are no subscribers) > Messages are being added to topic even if there are no subscribers > ------------------------------------------------------------------- > > Key: WFLY-13261 > URL: https://issues.redhat.com/browse/WFLY-13261 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 19.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > > After applying EAP 7.2 Update 7 , messages seem to be added to a topic even when there are no subscribers on the topic. > When subscribers are attached to a topic they seem to consume messages from a topic but the messages is not removed from the underlying physical queue resulting in the destination growing indefinitely in size. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13261) [GSS](7.2.z) Messages are being added to topic even if there are no subscribers

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13261?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet moved JBEAP-19003 to WFLY-13261: -------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13261 (was: JBEAP-19003) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) Affects Version/s: 19.0.0.Final (was: 7.2.6.GA) > [GSS](7.2.z) Messages are being added to topic even if there are no subscribers > -------------------------------------------------------------------------------- > > Key: WFLY-13261 > URL: https://issues.redhat.com/browse/WFLY-13261 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 19.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Blocker > > After applying EAP 7.2 Update 7 , messages seem to be added to a topic even when there are no subscribers on the topic. > When subscribers are attached to a topic they seem to consume messages from a topic but the messages is not removed from the underlying physical queue resulting in the destination growing indefinitely in size. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4135) Support for read only server configuration directory

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFCORE-4135?page=com.atlassian.jira.plug... ] Yeray Borges Santana updated WFCORE-4135: ----------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3531, https://github.com/wildfly/wildfly-core/pull/4104 (was: https://github.com/wildfly/wildfly-core/pull/3531) > Support for read only server configuration directory > ---------------------------------------------------- > > Key: WFCORE-4135 > URL: https://issues.redhat.com/browse/WFCORE-4135 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Rafael Ruiz > Assignee: Yeray Borges Santana > Priority: Major > > -We need something like- > ---disable-configuration-history- > -to use when running in containers to avoid write to any directory ('standalone_xml_history').- > History backups are senseless running on a container, and certain cloud use cases could require a non-writable storage mounted as a configuration directory. Also, when we are running on a non-containerized environment we could have very strict security rules that could force us the use of a read-only configuration directory. > We need a solution to make the server able to work with read-only configuration directories. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5186) [DMN Designer] Scrolling outside of the Literal Expression section discard the data and immediately loose focus

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-5186?page=com.atlassian.jira.plug... ] Anna Dupliak updated DROOLS-5186: --------------------------------- Description: When User edit multy-linear Literal expression in some Descision And scrolls down (keeping the mouse pointer outside of Literal Expression area) Then focus is lost And last edited data are lost See: https://issues.redhat.com/secure/attachment/12468058/scrollInEditArea.webm was: When User edit multy-linear Literal expression in some Descision And scrolls down Then focus looses And User could not put any data to any edit field See: [^scroll.webm] Workaround: Logout and login back > [DMN Designer] Scrolling outside of the Literal Expression section discard the data and immediately loose focus > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-5186 > URL: https://issues.redhat.com/browse/DROOLS-5186 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.35.0.Final > Reporter: Anna Dupliak > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > When User edit multy-linear Literal expression in some Descision > And scrolls down (keeping the mouse pointer outside of Literal Expression area) > Then focus is lost > And last edited data are lost > See: https://issues.redhat.com/secure/attachment/12468058/scrollInEditArea.webm -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5186) [DMN Designer] Scrolling outside of the Literal Expression section discard the data and immediately loose focus

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-5186?page=com.atlassian.jira.plug... ] Anna Dupliak updated DROOLS-5186: --------------------------------- Steps to Reproduce: # Go to DMN file # Add *Decision* node # Add Literal expression # Add 5 lines of text # Scroll down outside Literal Expression area #Unexpected: focus and last edited data are lost was: # Go to DMN file # Add *Decision* node # Add Literal expression # Add 5 lines of text # Scroll down outside Literal Expression area #Unexpected: focus and data are lost > [DMN Designer] Scrolling outside of the Literal Expression section discard the data and immediately loose focus > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-5186 > URL: https://issues.redhat.com/browse/DROOLS-5186 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.35.0.Final > Reporter: Anna Dupliak > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > When User edit multy-linear Literal expression in some Descision > And scrolls down > Then focus looses > And User could not put any data to any edit field > See: [^scroll.webm] > Workaround: > Logout and login back -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5186) [DMN Designer] Scrolling outside of the Literal Expression section discard the data and immediately loose focus

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-5186?page=com.atlassian.jira.plug... ] Anna Dupliak updated DROOLS-5186: --------------------------------- Steps to Reproduce: # Go to DMN file # Add *Decision* node # Add Literal expression # Add 5 lines of text # Scroll down outside Literal Expression area #Unexpected: focus and data are lost was: # Go to DMN file # Add *Decision* node # Add Literal expression # Add 5 lines of text # Scroll down #Unexpected: focus is lost and user cannot put any data in any editor > [DMN Designer] Scrolling outside of the Literal Expression section discard the data and immediately loose focus > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-5186 > URL: https://issues.redhat.com/browse/DROOLS-5186 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.35.0.Final > Reporter: Anna Dupliak > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > When User edit multy-linear Literal expression in some Descision > And scrolls down > Then focus looses > And User could not put any data to any edit field > See: [^scroll.webm] > Workaround: > Logout and login back -- 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