August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4423) getObjectsDeep() leaks SubnetworkTuple instances

by Geoffrey De Smet (Jira)

[ https://issues.jboss.org/browse/DROOLS-4423?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-4423: ------------------------------------- Fix Version/s: 7.26.0.Final > getObjectsDeep() leaks SubnetworkTuple instances > ------------------------------------------------ > > Key: DROOLS-4423 > URL: https://issues.jboss.org/browse/DROOLS-4423 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Major > Fix For: 7.26.0.Final > > Attachments: bugReproducer with non-Engligsh characters removed.zip, bugReproducer.zip > > > https://stackoverflow.com/questions/57390971/optaplanner-i-tried-to-print... > Mario promised to take a look at fixing this if the user can provide a reproducer and they or QA isolate it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-927) Bash scripts called from jenkins pipeline can't use cd command

by Filip Brychta (Jira)

Filip Brychta created SWSQE-927: ----------------------------------- Summary: Bash scripts called from jenkins pipeline can't use cd command Key: SWSQE-927 URL: https://issues.jboss.org/browse/SWSQE-927 Project: Kiali QE Issue Type: Bug Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4435) Test Scenario: add validation during file loading to avoid an additional backend call

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4435: ------------------------------------- Summary: Test Scenario: add validation during file loading to avoid an additional backend call Key: DROOLS-4435 URL: https://issues.jboss.org/browse/DROOLS-4435 Project: Drools Issue Type: Enhancement Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-926) Fix test_service_detail_with_destination_rule e2e test

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-926?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-926: ------------------------------------- It's failing because of following: if service_details != None and len(service_details.get('destinationRules').get('items')) == 0: break Which is expecting 0 destination rules. Test creates and deletes one rule but does not expects other rules from previous tests. > Fix test_service_detail_with_destination_rule e2e test > ------------------------------------------------------ > > Key: SWSQE-926 > URL: https://issues.jboss.org/browse/SWSQE-926 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: automation > > The test is failing with Exception: Timed out waiting for destination rule deletion -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4434) Setup drools-wb for Sonar analysis

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4434: ---------------------------------------- Summary: Setup drools-wb for Sonar analysis Key: DROOLS-4434 URL: https://issues.jboss.org/browse/DROOLS-4434 Project: Drools Issue Type: Enhancement Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Configure drools-wb to enable sonarcloud analysis on it -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-926) Fix test_service_detail_with_destination_rule e2e test

by Filip Brychta (Jira)

Filip Brychta created SWSQE-926: ----------------------------------- Summary: Fix test_service_detail_with_destination_rule e2e test Key: SWSQE-926 URL: https://issues.jboss.org/browse/SWSQE-926 Project: Kiali QE Issue Type: Bug Reporter: Filip Brychta Assignee: Filip Brychta The test is failing with Exception: Timed out waiting for destination rule deletion -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11255) EE Concurrency Utilities Managed Executors / Thread Pool runtime stats

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11255?page=com.atlassian.jira.plugin... ] Eduardo Martins edited comment on WFLY-11255 at 8/14/19 5:14 AM: ----------------------------------------------------------------- Working PoC available at https://github.com/emmartins/wildfly/tree/WFLY-11255 , providing the following runtime stats: * completed tasks count * tasks count * threads count The stats above were already available to retrieve from the spec RI executors implementation, any other stat may require significant effort thus should IMHO be implemented as followup. More on this later tho, going to do analysis and confirm about effort needed to add other stats. was (Author: emmartins): Working PoC available at https://github.com/emmartins/wildfly/tree/WFLY-11255 , providing the following runtime stats: * completed tasks count * tasks count * threads count The stats above were already available to retrieve from the spec RI executors implementation, any other stat may require significant effort thus should IMHO be implemented as followup. > EE Concurrency Utilities Managed Executors / Thread Pool runtime stats > ---------------------------------------------------------------------- > > Key: WFLY-11255 > URL: https://issues.jboss.org/browse/WFLY-11255 > Project: WildFly > Issue Type: Feature Request > Components: Concurrency Utilities > Affects Versions: 14.0.0.Final > Reporter: Brad Maxwell > Assignee: Eduardo Martins > Priority: Major > > The managed executors / thread pools in the EE subsytem currently do not show any runtime information when invoked with include-runtime=true, the current thread pool size, queue length and such would be useful to check the performance and tuning. > {code} > /subsystem=ee/managed-executor-service=default:read-resource(include-runtime=true,recursive=true) > { > "outcome" => "success", > "result" => { > "context-service" => "default", > "core-threads" => undefined, > "hung-task-threshold" => 60000L, > "jndi-name" => "java:jboss/ee/concurrency/executor/default", > "keepalive-time" => 5000L, > "long-running-tasks" => false, > "max-threads" => undefined, > "queue-length" => undefined, > "reject-policy" => "ABORT", > "thread-factory" => undefined > } > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11255) EE Concurrency Utilities Managed Executors / Thread Pool runtime stats

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-11255?page=com.atlassian.jira.plugin... ] Eduardo Martins commented on WFLY-11255: ---------------------------------------- Working PoC available at https://github.com/emmartins/wildfly/tree/WFLY-11255 , providing the following runtime stats: * completed tasks count * tasks count * threads count The stats above were already available to retrieve from the spec RI executors implementation, any other stat may require significant effort thus should IMHO be implemented as followup. > EE Concurrency Utilities Managed Executors / Thread Pool runtime stats > ---------------------------------------------------------------------- > > Key: WFLY-11255 > URL: https://issues.jboss.org/browse/WFLY-11255 > Project: WildFly > Issue Type: Feature Request > Components: Concurrency Utilities > Affects Versions: 14.0.0.Final > Reporter: Brad Maxwell > Assignee: Eduardo Martins > Priority: Major > > The managed executors / thread pools in the EE subsytem currently do not show any runtime information when invoked with include-runtime=true, the current thread pool size, queue length and such would be useful to check the performance and tuning. > {code} > /subsystem=ee/managed-executor-service=default:read-resource(include-runtime=true,recursive=true) > { > "outcome" => "success", > "result" => { > "context-service" => "default", > "core-threads" => undefined, > "hung-task-threshold" => 60000L, > "jndi-name" => "java:jboss/ee/concurrency/executor/default", > "keepalive-time" => 5000L, > "long-running-tasks" => false, > "max-threads" => undefined, > "queue-length" => undefined, > "reject-policy" => "ABORT", > "thread-factory" => undefined > } > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12376) wildfly-ejb-client-bom does not manage org.jboss.ejb3:jboss-ejb3-ext-api anymore

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12376?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12376: ----------------------------------- Priority: Major (was: Blocker) > wildfly-ejb-client-bom does not manage org.jboss.ejb3:jboss-ejb3-ext-api anymore > -------------------------------------------------------------------------------- > > Key: WFLY-12376 > URL: https://issues.jboss.org/browse/WFLY-12376 > Project: WildFly > Issue Type: Bug > Components: BOM > Affects Versions: 17.0.1.Final > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > When using {{org.jboss.eap:wildfly-ejb-client-bom:7.3.0.CD17}}, {{org.jboss.ejb3:jboss-ejb3-ext-api}} is not provided anymore. This is a regression compared to {{org.jboss.eap:wildfly-ejb-client-bom:7.3.0.CD16}}. > From the user point of view, this will mean they will have to modify their existing applications to include version of this dependency, which is pretty bad UX. > The BOM is the only recommended and documented way to consume EJB client libraries in standalone applications, please see [Developing EJB Applications|https://access.redhat.com/documentation/en-us/red_hat_jboss_...]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12377) Document usage of JAXWS Client BOM in jaws-* quickstarts

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12377: -------------------------------------- Summary: Document usage of JAXWS Client BOM in jaws-* quickstarts Key: WFLY-12377 URL: https://issues.jboss.org/browse/WFLY-12377 Project: WildFly Issue Type: Enhancement Components: Quickstarts Reporter: Eduardo Martins Assignee: Eduardo Martins All JAXWS Quickstarts's readme.adoc should briefly introduce usage of the JAXWS Client BOM as the proper way to manage/use the dependencies in server, assuring compatibility with it. This new content should preferably be implemented through the import of a reusable section in /shared-docs. -- 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