May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3994) [DMN Designer] Connectors to do align with Node boundaries

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3994?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3994: ---------------------------------------- The problem is when the Connector is attached to the centre of the Shape. Hence this only affects re-opening diagrams authored in our editor where connectors were set to the _centre_. This can only be accomplished by connecting two {{Nodes}} and then dragging a connector end-point to the _centre_ of one of the {{Nodes}}. > [DMN Designer] Connectors to do align with Node boundaries > ---------------------------------------------------------- > > Key: DROOLS-3994 > URL: https://issues.jboss.org/browse/DROOLS-3994 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.21.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: DROOLS-3994-preview.png, connectors.png, traffic.dmn > > > When opening a DMN file the connectors do not align with the Node boundaries. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-734) Upload Jaeger Auatomation Runs Into Polarion

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-734: ------------------------------------- Summary: Upload Jaeger Auatomation Runs Into Polarion Key: SWSQE-734 URL: https://issues.jboss.org/browse/SWSQE-734 Project: Kiali QE Issue Type: QE Task Reporter: Matthew Mahoney Assignee: Kevin Earls Using the polarion_uploader, upload Jaeger automation runs into Polarion for TP releases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3432) While using the same template key with difference objects/attributes causes an exception when switching to the Data tab in a Guided Rule Template

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3432?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3432: -------------------------------- Tester: Jozef Marko (was: Lukáš Petrovický) > While using the same template key with difference objects/attributes causes an exception when switching to the Data tab in a Guided Rule Template > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3432 > URL: https://issues.jboss.org/browse/DROOLS-3432 > Project: Drools > Issue Type: Bug > Components: Guided Template Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > When we use the same template in key for different object fields(different fields from the same fields from different objects), we get an exception after selecting the data tab, attaching the screen shot. > There is a workaround , we can give every template a unique name as a work around, but this slow down because we need to create different key names with the same information in the data table. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-160) Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed

by Masafumi Miura (Jira)

[ https://issues.jboss.org/browse/REMJMX-160?page=com.atlassian.jira.plugin... ] Masafumi Miura updated REMJMX-160: ---------------------------------- Workaround Description: - Reuse a JMXConnector object after it's created via JMXConnectorFactory#connect(). - Pass a custom executor to JMXConnectorFactory.connect(url, map) by passing the environment map with the key "java.util.concurrent.Executor". See the attached JmxClientCustomExecutorWorkaround.java for details. was: - Reuse a JMXConnector object after it's created via JMXConnectorFactory#connect() - Pass a custom executor to JMXConnectorFactory.connect(url, map) by passing the environment map with the key "java.util.concurrent.Executor" > Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed > -------------------------------------------------------------------------------------- > > Key: REMJMX-160 > URL: https://issues.jboss.org/browse/REMJMX-160 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 1.1.3.Final, 3.0.1.Final > Reporter: Masafumi Miura > Assignee: JBoss SET > Priority: Major > Attachments: JmxClient.java, JmxClientCustomExecutorWorkaround.java, Memory.png, leaks.png > > > In JMX client application, every JMXConnectorFactory#connect() invocation creates a new ThreadGroup which is never reclaimed. > https://github.com/jbossas/remoting-jmx/blob/3.0.1.Final/src/main/java/or... > If a JMX client application lives for long periods of time and repeats to invoke JMXConnectorFactory#connect() and JMXConnector#close(), a lot of ThreadGroup instances are retained eventually. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-733) Add the Istio Ingress Route for Bookinfo on Kiali Checker

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-733: --------------------------------------------- Summary: Add the Istio Ingress Route for Bookinfo on Kiali Checker Key: SWSQE-733 URL: https://issues.jboss.org/browse/SWSQE-733 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Kiali Traffic Generator might use the istio ingress gateway instead of product page route. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-160) Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed

by Masafumi Miura (Jira)

[ https://issues.jboss.org/browse/REMJMX-160?page=com.atlassian.jira.plugin... ] Masafumi Miura updated REMJMX-160: ---------------------------------- Attachment: JmxClient.java > Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed > -------------------------------------------------------------------------------------- > > Key: REMJMX-160 > URL: https://issues.jboss.org/browse/REMJMX-160 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 1.1.3.Final, 3.0.1.Final > Reporter: Masafumi Miura > Assignee: JBoss SET > Priority: Major > Attachments: JmxClient.java, JmxClientCustomExecutorWorkaround.java, Memory.png, leaks.png > > > In JMX client application, every JMXConnectorFactory#connect() invocation creates a new ThreadGroup which is never reclaimed. > https://github.com/jbossas/remoting-jmx/blob/3.0.1.Final/src/main/java/or... > If a JMX client application lives for long periods of time and repeats to invoke JMXConnectorFactory#connect() and JMXConnector#close(), a lot of ThreadGroup instances are retained eventually. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-160) Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed

by Masafumi Miura (Jira)

[ https://issues.jboss.org/browse/REMJMX-160?page=com.atlassian.jira.plugin... ] Masafumi Miura updated REMJMX-160: ---------------------------------- Attachment: JmxClientCustomExecutorWorkaround.java > Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed > -------------------------------------------------------------------------------------- > > Key: REMJMX-160 > URL: https://issues.jboss.org/browse/REMJMX-160 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 1.1.3.Final, 3.0.1.Final > Reporter: Masafumi Miura > Assignee: JBoss SET > Priority: Major > Attachments: JmxClient.java, JmxClientCustomExecutorWorkaround.java, Memory.png, leaks.png > > > In JMX client application, every JMXConnectorFactory#connect() invocation creates a new ThreadGroup which is never reclaimed. > https://github.com/jbossas/remoting-jmx/blob/3.0.1.Final/src/main/java/or... > If a JMX client application lives for long periods of time and repeats to invoke JMXConnectorFactory#connect() and JMXConnector#close(), a lot of ThreadGroup instances are retained eventually. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-731) Kiali Traffic Generator - Not running

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-731?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-731: -------------------------------------- Traffic generator does not have a logs, as mentioned in description, the main pipeline fails, so this is the old-bookinfo, https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/old-bookinfo/32... > Kiali Traffic Generator - Not running > ------------------------------------- > > Key: SWSQE-731 > URL: https://issues.jboss.org/browse/SWSQE-731 > Project: Kiali QE > Issue Type: Bug > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > Labels: infrastructure > > Traffic Generator does not log any output and does not send any traffic. > This blocks bookinfo install job's checker, thus blocks PRT -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-160) Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed

by Masafumi Miura (Jira)

[ https://issues.jboss.org/browse/REMJMX-160?page=com.atlassian.jira.plugin... ] Masafumi Miura updated REMJMX-160: ---------------------------------- Workaround Description: - Reuse a JMXConnector object after it's created via JMXConnectorFactory#connect() - Pass a custom executor to JMXConnectorFactory.connect(url, map) by passing the environment map with the key "java.util.concurrent.Executor" was: - Reuse a JMXConnector object after it's created via JMXConnectorFactory#connect() - Pass a custom executor by the environment map with the key "java.util.concurrent.Executor" > Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed > -------------------------------------------------------------------------------------- > > Key: REMJMX-160 > URL: https://issues.jboss.org/browse/REMJMX-160 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 1.1.3.Final, 3.0.1.Final > Reporter: Masafumi Miura > Assignee: JBoss SET > Priority: Major > Attachments: Memory.png, leaks.png > > > In JMX client application, every JMXConnectorFactory#connect() invocation creates a new ThreadGroup which is never reclaimed. > https://github.com/jbossas/remoting-jmx/blob/3.0.1.Final/src/main/java/or... > If a JMX client application lives for long periods of time and repeats to invoke JMXConnectorFactory#connect() and JMXConnector#close(), a lot of ThreadGroup instances are retained eventually. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-160) Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed

by Masafumi Miura (Jira)

[ https://issues.jboss.org/browse/REMJMX-160?page=com.atlassian.jira.plugin... ] Masafumi Miura updated REMJMX-160: ---------------------------------- Workaround Description: - Reuse a JMXConnector object after it's created via JMXConnectorFactory#connect() - Pass a custom executor by the environment map with the key "java.util.concurrent.Executor" was:Reuse a JMXConnector object after it's created via JMXConnectorFactory#connect() > Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed > -------------------------------------------------------------------------------------- > > Key: REMJMX-160 > URL: https://issues.jboss.org/browse/REMJMX-160 > Project: Remoting JMX > Issue Type: Bug > Affects Versions: 1.1.3.Final, 3.0.1.Final > Reporter: Masafumi Miura > Assignee: JBoss SET > Priority: Major > Attachments: Memory.png, leaks.png > > > In JMX client application, every JMXConnectorFactory#connect() invocation creates a new ThreadGroup which is never reclaimed. > https://github.com/jbossas/remoting-jmx/blob/3.0.1.Final/src/main/java/or... > If a JMX client application lives for long periods of time and repeats to invoke JMXConnectorFactory#connect() and JMXConnector#close(), a lot of ThreadGroup instances are retained eventually. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019