April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-703) Report results for system tests in internal sonar

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-703?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-703: ------------------------------------- Created https://projects.engineering.redhat.com/browse/CID-4148 > Report results for system tests in internal sonar > ------------------------------------------------- > > Key: SWSQE-703 > URL: https://issues.jboss.org/browse/SWSQE-703 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-686) UI Automation - Refresh Buttons

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-686?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-686. ---------------------------------- Resolution: Done > UI Automation - Refresh Buttons > ------------------------------- > > Key: SWSQE-686 > URL: https://issues.jboss.org/browse/SWSQE-686 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Verify Refresh Buttons on all List and Details pages. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3778) Receiving error InvocationTargetException on jdk11

by Yevgeniy Fomin (Jira)

[ https://issues.jboss.org/browse/DROOLS-3778?page=com.atlassian.jira.plugi... ] Yevgeniy Fomin updated DROOLS-3778: ----------------------------------- Sprint: 2019 Week 14-16 > Receiving error InvocationTargetException on jdk11 > -------------------------------------------------- > > Key: DROOLS-3778 > URL: https://issues.jboss.org/browse/DROOLS-3778 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.20.0.Final > Environment: * jdk11 > * Apache Maven 3.5.4 (Red Hat 3.5.4-4) > Reporter: Yevgeniy Fomin > Assignee: Yevgeniy Fomin > Priority: Major > Labels: drools-tools, jdk11 > Attachments: Error log powermock.txt > > > There is InvocationTargetException on test classes if they are run on jdk11. The tests can be found in [module|https://github.com/kiegroup/kie-wb-common/tree/master/kie-wb-commo...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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: ---------------------------------- Git Pull Request: https://github.com/jbossas/remoting-jmx/pull/36, https://github.com/jbossas/remoting-jmx/pull/37, https://github.com/jbossas/remoting-jmx/pull/38 > 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: Darran Lofthouse > Priority: Major > > 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, 1 month

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() (was: Reuse a JMXConnector object after it's created via JMXConnector#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: Darran Lofthouse > Priority: Major > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4405) Binary jar files in model-test

by Lin Gao (Jira)

Lin Gao created WFCORE-4405: ------------------------------- Summary: Binary jar files in model-test Key: WFCORE-4405 URL: https://issues.jboss.org/browse/WFCORE-4405 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: Lin Gao Assignee: Lin Gao Binary jar files are in model-test module, which will break the CC requirements in downstream project. It would be good to fix in upstream as well so that it won't be missing when new stream is created. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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: ---------------------------------- Description: 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. was: In JMX client application, every JMXConnector#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 JMXConnector#connect() and JMXConnector#close(), a lot of ThreadGroup instances are retained eventually. > 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: Darran Lofthouse > Priority: Major > > 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, 1 month

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: ---------------------------------- Summary: Every JMXConnectorFactory#connect() creates a new ThreadGroup which is never reclaimed (was: Every JMXConnector#connect() creates a new ThreadGroup which is never reclaimed) > 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: Darran Lofthouse > Priority: Major > > In JMX client application, every JMXConnector#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 JMXConnector#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, 1 month

1
0
0 / 0

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

by Masafumi Miura (Jira)

Masafumi Miura created REMJMX-160: ------------------------------------- Summary: Every JMXConnector#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: 3.0.1.Final, 1.1.3.Final Reporter: Masafumi Miura Assignee: Darran Lofthouse In JMX client application, every JMXConnector#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 JMXConnector#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, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-686) UI Automation - Refresh Buttons

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-686?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-686: -------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/157 > UI Automation - Refresh Buttons > ------------------------------- > > Key: SWSQE-686 > URL: https://issues.jboss.org/browse/SWSQE-686 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Verify Refresh Buttons on all List and Details pages. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 April 2019