August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4257) DMN UX - overlay information about an entire simulation execution

by Margot Menestrot (Jira)

[ https://issues.jboss.org/browse/DROOLS-4257?page=com.atlassian.jira.plugi... ] Margot Menestrot edited comment on DROOLS-4257 at 8/19/19 9:39 AM: ------------------------------------------------------------------- Prototype: https://marvelapp.com/1hd5b82g/screen/60431358 Steps: 1. Click on "View DMN diagram" button in global coverage report 2. Brought to DMN model view with highlights and icons to indicate where the test went right or wrong 3. Click on icons to see the exact errors in the test was (Author: mmenestr): Prototype: https://marvelapp.com/project/4281481/ Steps: 1. Click on "View DMN diagram" button in global coverage report 2. Brought to DMN model view with highlights and icons to indicate where the test went right or wrong 3. Click on icons to see the exact errors in the test > DMN UX - overlay information about an entire simulation execution > ----------------------------------------------------------------- > > Key: DROOLS-4257 > URL: https://issues.jboss.org/browse/DROOLS-4257 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Daniele Zonca > Assignee: Margot Menestrot > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Related to https://issues.jboss.org/browse/DROOLS-3731 > This task will cover this use case: > - user creates a DMN model > - user creates a Test Scenario with some scenarios > - user executes the Test Scenario > - user open Coverage Report > - user wants to analyze coverage information of {color:red}the *whole* simulation{color} > - user clicks on "a link" near global coverage information > - user lands on DMN editor with overlay information about number of time each decision has been executed, number of time each decision succeed/fail (maybe with different colors?) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4257) DMN UX - overlay information about an entire simulation execution

by Margot Menestrot (Jira)

[ https://issues.jboss.org/browse/DROOLS-4257?page=com.atlassian.jira.plugi... ] Margot Menestrot commented on DROOLS-4257: ------------------------------------------ Prototype: https://marvelapp.com/project/4281481/ Steps: 1. Click on "View DMN diagram" button in global coverage report 2. Brought to DMN model view with highlights and icons to indicate where the test went right or wrong 3. Click on icons to see the exact errors in the test > DMN UX - overlay information about an entire simulation execution > ----------------------------------------------------------------- > > Key: DROOLS-4257 > URL: https://issues.jboss.org/browse/DROOLS-4257 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Daniele Zonca > Assignee: Margot Menestrot > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Related to https://issues.jboss.org/browse/DROOLS-3731 > This task will cover this use case: > - user creates a DMN model > - user creates a Test Scenario with some scenarios > - user executes the Test Scenario > - user open Coverage Report > - user wants to analyze coverage information of {color:red}the *whole* simulation{color} > - user clicks on "a link" near global coverage information > - user lands on DMN editor with overlay information about number of time each decision has been executed, number of time each decision succeed/fail (maybe with different colors?) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-167) IllegalStateException: No standard field found for reverse order comparator!

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/REMJMX-167?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on REMJMX-167: ----------------------------------------- Can you please provide the full issue within the description in the Jira issue - issues requiring cross referencing of external sources to gain a basic understanding of the issue are hard to process. > IllegalStateException: No standard field found for reverse order comparator! > ---------------------------------------------------------------------------- > > Key: REMJMX-167 > URL: https://issues.jboss.org/browse/REMJMX-167 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 3.0.3.Final > Reporter: Andres Luuk > Priority: Major > > https://github.com/jbossas/remoting-jmx/issues/41 > You are also affected with: > https://developer.jboss.org/thread/279791 > https://209.132.182.82/browse/WFLY-11720?focusedCommentId=13697026&page=c... > jboss-marshalling should probably be updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-167) IllegalStateException: No standard field found for reverse order comparator!

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/REMJMX-167?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned REMJMX-167: --------------------------------------- Assignee: (was: Darran Lofthouse) > IllegalStateException: No standard field found for reverse order comparator! > ---------------------------------------------------------------------------- > > Key: REMJMX-167 > URL: https://issues.jboss.org/browse/REMJMX-167 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 3.0.3.Final > Reporter: Andres Luuk > Priority: Major > > https://github.com/jbossas/remoting-jmx/issues/41 > You are also affected with: > https://developer.jboss.org/thread/279791 > https://209.132.182.82/browse/WFLY-11720?focusedCommentId=13697026&page=c... > jboss-marshalling should probably be updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-167) IllegalStateException: No standard field found for reverse order comparator!

by Andres Luuk (Jira)

[ https://issues.jboss.org/browse/REMJMX-167?page=com.atlassian.jira.plugin... ] Andres Luuk updated REMJMX-167: ------------------------------- Issue Type: Bug (was: Feature Request) > IllegalStateException: No standard field found for reverse order comparator! > ---------------------------------------------------------------------------- > > Key: REMJMX-167 > URL: https://issues.jboss.org/browse/REMJMX-167 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 3.0.3.Final > Reporter: Andres Luuk > Assignee: Darran Lofthouse > Priority: Major > > https://github.com/jbossas/remoting-jmx/issues/41 > You are also affected with: > https://developer.jboss.org/thread/279791 > https://209.132.182.82/browse/WFLY-11720?focusedCommentId=13697026&page=c... > jboss-marshalling should probably be updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-167) IllegalStateException: No standard field found for reverse order comparator!

by Andres Luuk (Jira)

Andres Luuk created REMJMX-167: ---------------------------------- Summary: IllegalStateException: No standard field found for reverse order comparator! Key: REMJMX-167 URL: https://issues.jboss.org/browse/REMJMX-167 Project: Remoting JMX Issue Type: Feature Request Affects Versions: 3.0.3.Final Reporter: Andres Luuk Assignee: Darran Lofthouse https://github.com/jbossas/remoting-jmx/issues/41 You are also affected with: https://developer.jboss.org/thread/279791 https://209.132.182.82/browse/WFLY-11720?focusedCommentId=13697026&page=c... jboss-marshalling should probably be updated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-935) install-maistra does not support AWS

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-935: ------------------------------------- Summary: install-maistra does not support AWS Key: SWSQE-935 URL: https://issues.jboss.org/browse/SWSQE-935 Project: Kiali QE Issue Type: Task Reporter: Matthew Mahoney Assignee: Filip Brychta AWS clusters are not supported by install-maistra because there is no ability to login with username/password. AWS clusters need to be supported out of the box. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-166) IllegalThreadStateException after idle jmx connection

by Märt Bakhoff (Jira)

Märt Bakhoff created REMJMX-166: ----------------------------------- Summary: IllegalThreadStateException after idle jmx connection Key: REMJMX-166 URL: https://issues.jboss.org/browse/REMJMX-166 Project: Remoting JMX Issue Type: Bug Components: Connection Affects Versions: 3.0.3.Final, 3.0.2.Final Environment: org.jboss.remotingjmx:remoting-jmx:3.0.3.Final + java8 Reporter: Märt Bakhoff Assignee: Darran Lofthouse Start wildfly-17.0.1/bin/standalone.sh, then run this code snippet: {noformat} JMXServiceURL url = new JMXServiceURL("service:jmx:remote+http://127.0.0.1:9990"); try (JMXConnector connector = new RemotingConnectorProvider().newJMXConnector(url, Collections.emptyMap())) { connector.connect(); MBeanServerConnection beanServer = connector.getMBeanServerConnection(); RuntimeMXBean bean = ManagementFactory.newPlatformMXBeanProxy(beanServer, ManagementFactory.RUNTIME_MXBEAN_NAME, RuntimeMXBean.class); Thread.sleep(70_000); System.out.println("uptime: " + bean.getUptime()); } {noformat} The following exception is always thrown: {noformat} Exception in thread "XNIO-1 task-12" java.lang.IllegalThreadStateException at java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867) at java.lang.Thread.init(Thread.java:405) at java.lang.Thread.init(Thread.java:349) at java.lang.Thread.<init>(Thread.java:599) at org.jboss.remotingjmx.protocol.v2.ClientExecutorManager$1.newThread(ClientExecutorManager.java:56) at java.util.concurrent.ThreadPoolExecutor$Worker.<init>(ThreadPoolExecutor.java:619) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:932) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1378) at org.jboss.remotingjmx.protocol.v2.ClientExecutorManager.execute(ClientExecutorManager.java:64) at org.jboss.remotingjmx.protocol.v2.ClientCommon$MessageReceiver.handleMessage(ClientCommon.java:118) at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {noformat} The cause is in org.jboss.remotingjmx.protocol.v2.ClientExecutorManager.<init>. It creates a thread pool with Executors.newCachedThreadPool that has the default keepAliveTime of 60s. The thread factory is using a daemon thread group REMOTING_JMX that will self-destruct when the cached thread is terminated. The same code works when using older org.jboss.remotingjmx:remoting-jmx:3.0.1.Final. The regression is likely caused by commit https://github.com/jbossas/remoting-jmx/commit/2d6ae6c26da43304b752fc48f1... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2372) LeaveTest fails frequently

by Bela Ban (Jira)

Bela Ban created JGRP-2372: ------------------------------ Summary: LeaveTest fails frequently Key: JGRP-2372 URL: https://issues.jboss.org/browse/JGRP-2372 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Ditto for ASYM_ENCRYPT_LeaveTest and ASYM_ENCRYPT_LeaveTestKeyExchange. Multiple members leaving seems to leave some members behind; the view is never correct. This happens only when running the entire test suite; running a test individually, or running all encryption tests ({{ant encrypt}}) almost never reproduces the errors. This is possibly caused by the high load of running a lot of tests concurrently, and the subsequent delays resulting from it. Nevertheless, these tests should not fail. Error message: {noformat} Timeout 30000 kicked in, views are: 9: [7|15] (4) [7, 8, 9, 10] 10: [7|15] (4) [7, 8, 9, 10] java.util.concurrent.TimeoutException at org.jgroups.util.Util.waitUntilAllChannelsHaveSameView(Util.java:293) at org.jgroups.tests.BaseLeaveTest.testConcurrentLeaves(BaseLeaveTest.java:189) at org.jgroups.tests.BaseLeaveTest.testLeaveOfFirstNMembers(BaseLeaveTest.java:214) at org.jgroups.tests.BaseLeaveTest.testLeaveOfCoordAndNext8(BaseLeaveTest.java:146) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:124) at org.testng.internal.Invoker.invokeMethod(Invoker.java:583) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:719) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:989) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2372) LeaveTest fails frequently

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2372?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2372: --------------------------- Fix Version/s: 4.1.4 > LeaveTest fails frequently > -------------------------- > > Key: JGRP-2372 > URL: https://issues.jboss.org/browse/JGRP-2372 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.4 > > > Ditto for ASYM_ENCRYPT_LeaveTest and ASYM_ENCRYPT_LeaveTestKeyExchange. Multiple members leaving seems to leave some members behind; the view is never correct. > This happens only when running the entire test suite; running a test individually, or running all encryption tests ({{ant encrypt}}) almost never reproduces the errors. > This is possibly caused by the high load of running a lot of tests concurrently, and the subsequent delays resulting from it. Nevertheless, these tests should not fail. > Error message: > {noformat} > Timeout 30000 kicked in, views are: 9: [7|15] (4) [7, 8, 9, 10] 10: [7|15] (4) [7, 8, 9, 10] > java.util.concurrent.TimeoutException > at org.jgroups.util.Util.waitUntilAllChannelsHaveSameView(Util.java:293) > at org.jgroups.tests.BaseLeaveTest.testConcurrentLeaves(BaseLeaveTest.java:189) > at org.jgroups.tests.BaseLeaveTest.testLeaveOfFirstNMembers(BaseLeaveTest.java:214) > at org.jgroups.tests.BaseLeaveTest.testLeaveOfCoordAndNext8(BaseLeaveTest.java:146) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:124) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:583) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:719) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:989) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019