July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2743) [DMN Designer] Switch grid toolbar button

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2743: ----------------------------------- Summary: [DMN Designer] Switch grid toolbar button Key: DROOLS-2743 URL: https://issues.jboss.org/browse/DROOLS-2743 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.9.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Priority: Minor The stunner based designers contain "Switch grid" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button. It would be more logical to disable this button while expression editor is opened as the grid is not shown at that moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2742) [DMN Designer] Switch grid toolbar button

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2742?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2742: -------------------------------- Description: The stunner based designers contain "Switch grid" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button. It would be more logical to disable this button while expression editor is opened as the grid is not shown at that moment. (was: The stunner based designers contain "Clear the diagram" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button and thus can clear node that he currently edits. I think we should disable that button if expression editor is opened.) > [DMN Designer] Switch grid toolbar button > ----------------------------------------- > > Key: DROOLS-2742 > URL: https://issues.jboss.org/browse/DROOLS-2742 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > The stunner based designers contain "Switch grid" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button. It would be more logical to disable this button while expression editor is opened as the grid is not shown at that moment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2742) [DMN Designer] Clear the diagram toolbar button

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2742: ----------------------------------- Summary: [DMN Designer] Clear the diagram toolbar button Key: DROOLS-2742 URL: https://issues.jboss.org/browse/DROOLS-2742 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.9.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Priority: Minor The stunner based designers contain "Clear the diagram" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button and thus can clear node that he currently edits. I think we should disable that button if expression editor is opened. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2742) [DMN Designer] Switch grid toolbar button

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2742?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2742: -------------------------------- Summary: [DMN Designer] Switch grid toolbar button (was: [DMN Designer] Clear the diagram toolbar button) > [DMN Designer] Switch grid toolbar button > ----------------------------------------- > > Key: DROOLS-2742 > URL: https://issues.jboss.org/browse/DROOLS-2742 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > The stunner based designers contain "Clear the diagram" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button and thus can clear node that he currently edits. I think we should disable that button if expression editor is opened. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2741) [DMN Designer] Clear the diagram toolbar button

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2741: ----------------------------------- Summary: [DMN Designer] Clear the diagram toolbar button Key: DROOLS-2741 URL: https://issues.jboss.org/browse/DROOLS-2741 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.9.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Priority: Minor The stunner based designers contain "Clear the diagram" button. The problem of this button for DMN Designer appears if the expression editor is opened. User has still possibility to use this button and thus can clear node that he currently edits. I think we should disable that button if expression editor is opened. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2565) [DMN Editor] Move showcase webapp to "project" based instead of "standalone"

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2565?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2565: -------------------------------- Labels: drools-tools (was: ) > [DMN Editor] Move showcase webapp to "project" based instead of "standalone" > ---------------------------------------------------------------------------- > > Key: DROOLS-2565 > URL: https://issues.jboss.org/browse/DROOLS-2565 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > The DMN standalone showcase webapp does not integrate well into the Workbench as it has a bunch of custom component supporting basic file creation, loading etc. Before we can integrate the DMN Editor into the Workbench (so people can start looking at it) the showcase should be moved to be "project" centric. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2566) [DMN Editor] Integrate Editor into Workbench

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2566?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2566: -------------------------------- Issue Type: Epic (was: Feature Request) > [DMN Editor] Integrate Editor into Workbench > -------------------------------------------- > > Key: DROOLS-2566 > URL: https://issues.jboss.org/browse/DROOLS-2566 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > Following https://issues.jboss.org/browse/DROOLS-2565 we can integrate the DMN Editor into the Workbench - adding support to enable/disable the Editor (disabled by default). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2566) [DMN Editor] Integrate Editor into Workbench

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2566?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2566: -------------------------------- Epic Name: [DMN Editor] Integrate Editor into Workbench > [DMN Editor] Integrate Editor into Workbench > -------------------------------------------- > > Key: DROOLS-2566 > URL: https://issues.jboss.org/browse/DROOLS-2566 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > Following https://issues.jboss.org/browse/DROOLS-2565 we can integrate the DMN Editor into the Workbench - adding support to enable/disable the Editor (disabled by default). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2566) [DMN Editor] Integrate Editor into Workbench

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2566?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2566: -------------------------------- Labels: drools-tools (was: ) > [DMN Editor] Integrate Editor into Workbench > -------------------------------------------- > > Key: DROOLS-2566 > URL: https://issues.jboss.org/browse/DROOLS-2566 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: drools-tools > > Following https://issues.jboss.org/browse/DROOLS-2565 we can integrate the DMN Editor into the Workbench - adding support to enable/disable the Editor (disabled by default). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10474) AMQ119012: Timed out waiting to receive initial broadcast from cluster

by Erich Duda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10474?page=com.atlassian.jira.plugin... ] Erich Duda commented on WFLY-10474: ----------------------------------- I managed to reproduce the issue with WF12 so the reproducer is valid. > AMQ119012: Timed out waiting to receive initial broadcast from cluster > ---------------------------------------------------------------------- > > Key: WFLY-10474 > URL: https://issues.jboss.org/browse/WFLY-10474 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 13.0.0.Beta1 > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: blocker-WF14 > > In messaging HA scenarios we see that tests sometimes fail because of exception \[1\]. The exception is thrown from {{ServerLocatorImpl::createSessionFactory}} which waits until initial broadcast from cluster is received, but it is not received in 10 seconds timeout. In following scenario the issue causes split brain - both live and backup are active at the same time. > *Scenario* > * There are two Wildfly/Artemis servers configured as Live-Backup pair > * Live server is killed > * Backup server becomes new Live server > * Live server is restarted and failback is performed > *Expectation:* Failback performs successfully. Original Live becomes Live again and original Backup becomes Backup again. > *Reality:* After the Live is restarted, it does not detect that there is already another active Live with the same nodeId and it activates (becomes Live) so both Live and Backup are active at the same time. > *Technical details* > I found out that original Live server does not detect that its Backup is active, because SharedNothingLiveActivation::isNodeIdUsed returns false. I added more logs to this method and found out that the {{false}} is returned from line \[2\] after that the exception \[1\] is thrown. > *Investigation report* > I tried to downgrade Artemis to {{1.5.5.jbossorg-010}} version but I hit the same issue. So the issue is not caused by recent Artemis upgrade. > It is regression against EAP 7.1.0.GA but it is not regression against Wildfly 12. > We see the issue only with JGroups. I tried to run the test with Netty discovery and it passed 50 times in row. > \[1\] > {code} > ActiveMQConnectionTimedOutException[errorType=CONNECTION_TIMEDOUT message=AMQ119012: Timed out waiting to receive initial broadcast from cluster] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:749) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:627) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connectNoWarnings(ServerLocatorImpl.java:633) [artemis-core-client-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation.isNodeIdUsed(SharedNothingLiveActivation.java:280) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.server.impl.SharedNothingLiveActivation.run(SharedNothingLiveActivation.java:90) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:539) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:485) [artemis-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:413) [artemis-jms-server-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-SNAPSHOT] > at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:205) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT] > at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:64) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT] > at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:99) [wildfly-messaging-activemq-13.0.0.Beta2-SNAPSHOT.jar:13.0.0.Beta2-SNAPSHOT] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_171] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_171] > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.3.2.Final.jar:2.3.2.Final] > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) [jboss-threads-2.3.2.Final.jar:2.3.2.Final] > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) [jboss-threads-2.3.2.Final.jar:2.3.2.Final] > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) [jboss-threads-2.3.2.Final.jar:2.3.2.Final] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171] > at org.jboss.threads.JBossThread.run(JBossThread.java:485) [jboss-threads-2.3.2.Final.jar:2.3.2.Final] > {code} > \[2\] https://github.com/rh-messaging/jboss-activemq-artemis/blob/465eb8733e465... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 July 2018