February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3062) [DMN Designer] [UX] Automatic layout feature prompt

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3062?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3062: ------------------------------------- [~dadossan] Some of the better icons are already being used in the UI. For the toolbar icon that would represent "organize this diagram for me" how about one of these: 1) https://fontawesome.com/icons/crosshairs?style=solid - or - 2) Although it's already being used in the tree, maybe we could reuse: https://fontawesome.com/icons/project-diagram?style=solid Wdyt? > [DMN Designer] [UX] Automatic layout feature prompt > --------------------------------------------------- > > Key: DROOLS-3062 > URL: https://issues.jboss.org/browse/DROOLS-3062 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Liz Clayton > Priority: Major > Labels: UX, drools-tools > > User should be able to invoke automatic layout feature anytime during diagram design phase. There should appear prompt that would explain the autolayout feature. > Please propose the the prompt. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3062) [DMN Designer] [UX] Automatic layout feature prompt

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3062?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3062: -------------------------------- Story Points: 1 > [DMN Designer] [UX] Automatic layout feature prompt > --------------------------------------------------- > > Key: DROOLS-3062 > URL: https://issues.jboss.org/browse/DROOLS-3062 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Liz Clayton > Priority: Major > Labels: UX, drools-tools > > User should be able to invoke automatic layout feature anytime during diagram design phase. There should appear prompt that would explain the autolayout feature. > Please propose the the prompt. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11682) Clustered SLSB membership anomalies when all cluster members removed

by Jörg Bäsner (Jira)

[ https://issues.jboss.org/browse/WFLY-11682?page=com.atlassian.jira.plugin... ] Jörg Bäsner updated WFLY-11682: ------------------------------- Description: This description will be based on a 3 node cluster. Cluster node 1 and 2 are configured in the {{PROVIDER_URL}}, node 3 is not. The client has a custom ClusterNodeSelector implementation that is printing the {{connectedNodes}} and the {{availableNodes}} and doing a random balancing. As long as all nodes are up and running the client is calling EJBs in a balanced way. When node1 is shut down, the client get the notification below: {code}... DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-4) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-4) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node1) DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node1) ... {code} Then node2 is shut down. Again the client get the information, see: {code} ... DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node2) ... {code} Finally node3 is being shut down. Now the client only get the following information: {code} ... DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground ... {code} This mean the _node3_ is not being informed about the fact that the last node of the cluster has been stopped. >From this point on the client is always getting {{Caused by: java.net.ConnectException: Connection refused}} Now node1 is started again, resulting in the following output for {{connectedNodes}} and the {{availableNodes}}: {code} ... INFO (ThreadPoolTaskExecutor-1) [com.jboss.examples.ejb.CustomClusterNodeSelector] connectedNodes(1) '[node1]', availableNodes(2) '[node3, node1]' ... {code} was: This description will be based on a 3 node cluster. Cluster node 1 and 2 are configured in the {{PROVIDER_URL}}, node 3 is not. The client has a custom ClusterNodeSelector implementation that is printing the {{connectedNodes}} and the {{availableNodes}} and doing a random balancing. As long as all nodes are up and running the client is calling EJBs in a balanced way. When node1 is shut down, the client get the notification below: {code}... DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-4) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-4) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node1) DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node1) ... {code} Then node2 is shut down. Again the client get the information, see: {code} ... DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node2) ... {code} Finally node3 is being shut down. Now the client only get the following information: {code} ... DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground ... {code} This mean the _node3_ is not being informed about the fact that the last node of the cluster has been stopped. >From this point on the client is always getting {{Caused by: java.net.ConnectException: Connection refused}} Now node1 is started again, resulting in the following output for {{connectedNodes}} and the {{availableNodes}}: {code} ... INFO (ThreadPoolTaskExecutor-1) [com.jboss.examples.ejb.LBClusterNodeSelector] connectedNodes(1) '[node1]', availableNodes(2) '[node3, node1]' ... {code} > Clustered SLSB membership anomalies when all cluster members removed > -------------------------------------------------------------------- > > Key: WFLY-11682 > URL: https://issues.jboss.org/browse/WFLY-11682 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 15.0.1.Final > Environment: WildFly running in an n-node cluster with an EJB client sending requests even during the time the cluster is down. > Reporter: Jörg Bäsner > Assignee: Richard Achmatowicz > Priority: Major > Attachments: playground.zip > > > This description will be based on a 3 node cluster. Cluster node 1 and 2 are configured in the {{PROVIDER_URL}}, node 3 is not. > The client has a custom ClusterNodeSelector implementation that is printing the {{connectedNodes}} and the {{availableNodes}} and doing a random balancing. > As long as all nodes are up and running the client is calling EJBs in a balanced way. > When node1 is shut down, the client get the notification below: > {code}... > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-4) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-4) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node1) > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node1) > ... > {code} > Then node2 is shut down. Again the client get the information, see: > {code} > ... > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received CLUSTER_TOPOLOGY_NODE_REMOVAL(18) message for (cluster, node) = (ejb, node2) > ... > {code} > Finally node3 is being shut down. Now the client only get the following information: > {code} > ... > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > DEBUG (XNIO-1 task-1) [org.jboss.ejb.client.invocation] Received MODULE_UNAVAILABLE(9) message for module /playground > ... > {code} > This mean the _node3_ is not being informed about the fact that the last node of the cluster has been stopped. > From this point on the client is always getting {{Caused by: java.net.ConnectException: Connection refused}} > Now node1 is started again, resulting in the following output for {{connectedNodes}} and the {{availableNodes}}: > {code} > ... > INFO (ThreadPoolTaskExecutor-1) [com.jboss.examples.ejb.CustomClusterNodeSelector] connectedNodes(1) '[node1]', availableNodes(2) '[node3, node1]' > ... > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4314) Enchance keystore CLI commands

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4314?page=com.atlassian.jira.plugi... ] Farah Juma commented on WFCORE-4314: ------------------------------------ [~baranowb] It would probably be good to take a look at the output of the {{keytool -list}} command since the {{read-aliases}} and {{read-alias}} operations are intended to provide similar information. > Enchance keystore CLI commands > ------------------------------ > > Key: WFCORE-4314 > URL: https://issues.jboss.org/browse/WFCORE-4314 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4314) Enchance keystore CLI commands

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFCORE-4314?page=com.atlassian.jira.plugi... ] Farah Juma moved ELY-1750 to WFCORE-4314: ----------------------------------------- Project: WildFly Core (was: WildFly Elytron) Key: WFCORE-4314 (was: ELY-1750) Component/s: Security (was: Command-Line Tool) > Enchance keystore CLI commands > ------------------------------ > > Key: WFCORE-4314 > URL: https://issues.jboss.org/browse/WFCORE-4314 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1750) Enchance keystore CLI commands

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1750?page=com.atlassian.jira.plugin.s... ] Farah Juma commented on ELY-1750: --------------------------------- Going to move this one over to WFCORE since the code for these management operations is in the Elytron subsystem. > Enchance keystore CLI commands > ------------------------------ > > Key: ELY-1750 > URL: https://issues.jboss.org/browse/ELY-1750 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Command-Line Tool > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1711) Convert WildFly Elytron to a multi-module project

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1711?page=com.atlassian.jira.plugin.s... ] Farah Juma resolved ELY-1711. ----------------------------- Resolution: Done > Convert WildFly Elytron to a multi-module project > ------------------------------------------------- > > Key: ELY-1711 > URL: https://issues.jboss.org/browse/ELY-1711 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.9.0.CR1, 2.0.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1711) Convert WildFly Elytron to a multi-module project

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1711?page=com.atlassian.jira.plugin.s... ] Farah Juma commented on ELY-1711: --------------------------------- Going to mark this one as resolved as we now have new issues created to track the remaining work. > Convert WildFly Elytron to a multi-module project > ------------------------------------------------- > > Key: ELY-1711 > URL: https://issues.jboss.org/browse/ELY-1711 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 2.0.0.Alpha1, 1.9.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3062) [DMN Designer] [UX] Automatic layout feature prompt

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3062?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3062: ------------------------------------- [~dadossan] Not sure if you need anything from UX for this or not. If not, let me know so we can close this jira. Thanks! > [DMN Designer] [UX] Automatic layout feature prompt > --------------------------------------------------- > > Key: DROOLS-3062 > URL: https://issues.jboss.org/browse/DROOLS-3062 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Liz Clayton > Priority: Major > Labels: UX, drools-tools > > User should be able to invoke automatic layout feature anytime during diagram design phase. There should appear prompt that would explain the autolayout feature. > Please propose the the prompt. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1711) Convert WildFly Elytron to a multi-module project

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1711?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1711: ---------------------------- Fix Version/s: 2.0.0.Alpha1 > Convert WildFly Elytron to a multi-module project > ------------------------------------------------- > > Key: ELY-1711 > URL: https://issues.jboss.org/browse/ELY-1711 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 2.0.0.Alpha1, 1.9.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 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 2019