January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4576) Data object selector Search widget not enabled in saved tests

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4576?page=com.atlassian.jira.plug... ] Yeser Amer edited comment on DROOLS-4576 at 1/16/20 9:26 AM: ------------------------------------------------------------- Tech comments: Basically, the search should be enabled not only when an empty column is selected. It should store the inserted key during grid switch. DROOLS-4823 was (Author: yamer): Tech comments: Basically, the search should be enabled not only when an empty column is selected. It should store the inserted key during grid switch. > Data object selector Search widget not enabled in saved tests > ------------------------------------------------------------- > > Key: DROOLS-4576 > URL: https://issues.redhat.com/browse/DROOLS-4576 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: 2019-09-27 13.36.19.gif > > > The Search widget doesn't work (isn't accessible/enabled) in a test template that has been setup/saved, it does work in a new test though. Example attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4576) Data object selector Search widget not enabled in saved tests

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4576?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4576: ------------------------------------ Tech comments: Basically, the search should be enabled not only when an empty column is selected. It should store the inserted key during grid switch. > Data object selector Search widget not enabled in saved tests > ------------------------------------------------------------- > > Key: DROOLS-4576 > URL: https://issues.redhat.com/browse/DROOLS-4576 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: 2019-09-27 13.36.19.gif > > > The Search widget doesn't work (isn't accessible/enabled) in a test template that has been setup/saved, it does work in a new test though. Example attached. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4823) Improve "Search" functionality

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4823?page=com.atlassian.jira.plug... ] Yeser Amer closed DROOLS-4823. ------------------------------ Release Notes Text: Duplicate of DROOLS-4576 Resolution: Duplicate Issue > Improve "Search" functionality > ------------------------------ > > Key: DROOLS-4823 > URL: https://issues.redhat.com/browse/DROOLS-4823 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, ScenarioSimulationTeam, drools-tools > > Basically, the search should be enabled not only when a column is selected. > It should store the inserted key during grid switch. > Reported in DROOLS-4804 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2384) Remove deprecated classes

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2384?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2384. ---------------------------- Resolution: Done > Remove deprecated classes > ------------------------- > > Key: JGRP-2384 > URL: https://issues.redhat.com/browse/JGRP-2384 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0 > > > * All classes marked as {{@Deprecated}} > * {{FRAG}} > * {{FD}} > Update documentation, too -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1052) Uninstallation of istio leaves cluster in broken state

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1052?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1052. ---------------------------------- Resolution: Done Caused by https://github.com/istio/istio/issues/20238 Added workaround > Uninstallation of istio leaves cluster in broken state > ------------------------------------------------------ > > Key: SWSQE-1052 > URL: https://issues.redhat.com/browse/SWSQE-1052 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > When the upstream istio is removed from cluster it leaves the cluster in broken state. > New pods fail to start with: > (combined from similar events): Failed create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_registry-puller-89bd55495-8qc6s_registry-puller_b0cf5e01-383d-11ea-93d2-fa163ee5acb3_0(d93218e9cc51c4a6ed1a49829e9983d01ba0071bea5bb55dfadbac9345aa3996): Multus: Err adding pod to network "k8s-pod-network": Multus: error in invoke Conflist add - "k8s-pod-network": error in getting result from AddNetworkList: failed to find plugin "istio-cni" in path [/var/lib/cni/bin /opt/multus/bin] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12982) MP fault tolerance: CDI contexts not available in @Timeout methods

by Ladislav Thon (Jira)

[ https://issues.redhat.com/browse/WFLY-12982?page=com.atlassian.jira.plugi... ] Ladislav Thon commented on WFLY-12982: -------------------------------------- Indeed the new implementation should address this. > MP fault tolerance: CDI contexts not available in @Timeout methods > ------------------------------------------------------------------ > > Key: WFLY-12982 > URL: https://issues.redhat.com/browse/WFLY-12982 > Project: WildFly > Issue Type: Bug > Components: MP Fault Tolerance > Affects Versions: 19.0.0.Beta1 > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Major > > Say I have a {{@Timeout}} method in my application, which uses a {{@RequestScoped}} service: > {code:java} > @Inject > private MyService service; > @Timeout > public String doSomething() throws InterruptedException { > return "Hello " + service.call(); > } > {code} > The method isn't {{@Asynchronous}}, so it's supposed to be executed on the caller thread and hence the CDI contexts should be available. However, they are not: > {code} > 2018-04-03 21:16:35,976 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped > {code} > Clearly the {{@Timeout}} methods are always executed on a separate thread (see {{HystrixCommandInterceptor.initSetter}}): > {code:java} > // Async and timeout operations use THREAD isolation strategy > if (operation.isAsync() || operation.hasTimeout()) { > propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.THREAD); > } else { > propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.SEMAPHORE); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4927) Memory leak in PrometheusKieServerExtension

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-4927?page=com.atlassian.jira.plug... ] Luca Molteni reassigned DROOLS-4927: ------------------------------------ Assignee: Luca Molteni (was: Maciej Swiderski) > Memory leak in PrometheusKieServerExtension > ------------------------------------------- > > Key: DROOLS-4927 > URL: https://issues.redhat.com/browse/DROOLS-4927 > Project: Drools > Issue Type: Bug > Components: kie server > Affects Versions: 7.31.0.Final > Reporter: Karel Suta > Assignee: Luca Molteni > Priority: Major > > Prometheus Kie server extensions contains support for custom metrics [1]. > These metrics are added when a new container is called [2]. > However when container is removed then these metrics stay active. Agenda event listener has container instance as a HashMap key. This container instance is quite big, causing memory leak. > [1] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... > [2] https://github.com/kiegroup/droolsjbpm-integration/blob/master/kie-server... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12982) MP fault tolerance: CDI contexts not available in @Timeout methods

by Miroslav Novak (Jira)

[ https://issues.redhat.com/browse/WFLY-12982?page=com.atlassian.jira.plugi... ] Miroslav Novak commented on WFLY-12982: --------------------------------------- This is known issue THORN-1930 with MP FT. Cloning to WFLY as with new MP FT implementation this might be solved. > MP fault tolerance: CDI contexts not available in @Timeout methods > ------------------------------------------------------------------ > > Key: WFLY-12982 > URL: https://issues.redhat.com/browse/WFLY-12982 > Project: WildFly > Issue Type: Bug > Components: MP Fault Tolerance > Affects Versions: 19.0.0.Beta1 > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Major > > Say I have a {{@Timeout}} method in my application, which uses a {{@RequestScoped}} service: > {code:java} > @Inject > private MyService service; > @Timeout > public String doSomething() throws InterruptedException { > return "Hello " + service.call(); > } > {code} > The method isn't {{@Asynchronous}}, so it's supposed to be executed on the caller thread and hence the CDI contexts should be available. However, they are not: > {code} > 2018-04-03 21:16:35,976 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped > {code} > Clearly the {{@Timeout}} methods are always executed on a separate thread (see {{HystrixCommandInterceptor.initSetter}}): > {code:java} > // Async and timeout operations use THREAD isolation strategy > if (operation.isAsync() || operation.hasTimeout()) { > propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.THREAD); > } else { > propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.SEMAPHORE); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12982) MP fault tolerance: CDI contexts not available in @Timeout methods

by Miroslav Novak (Jira)

Miroslav Novak created WFLY-12982: ------------------------------------- Summary: MP fault tolerance: CDI contexts not available in @Timeout methods Key: WFLY-12982 URL: https://issues.redhat.com/browse/WFLY-12982 Project: WildFly Issue Type: Bug Components: MP Fault Tolerance Affects Versions: 19.0.0.Beta1 Reporter: Miroslav Novak Assignee: Radoslav Husar Say I have a {{@Timeout}} method in my application, which uses a {{@RequestScoped}} service: {code:java} @Inject private MyService service; @Timeout public String doSomething() throws InterruptedException { return "Hello " + service.call(); } {code} The method isn't {{@Asynchronous}}, so it's supposed to be executed on the caller thread and hence the CDI contexts should be available. However, they are not: {code} 2018-04-03 21:16:35,976 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped {code} Clearly the {{@Timeout}} methods are always executed on a separate thread (see {{HystrixCommandInterceptor.initSetter}}): {code:java} // Async and timeout operations use THREAD isolation strategy if (operation.isAsync() || operation.hasTimeout()) { propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.THREAD); } else { propertiesSetter.withExecutionIsolationStrategy(HystrixCommandProperties.ExecutionIsolationStrategy.SEMAPHORE); } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-299) MicroProfile OpenAPI: validate generated OpenAPI document

by Martin Svehla (Jira)

Martin Svehla created WFWIP-299: ----------------------------------- Summary: MicroProfile OpenAPI: validate generated OpenAPI document Key: WFWIP-299 URL: https://issues.redhat.com/browse/WFWIP-299 Project: WildFly WIP Issue Type: Enhancement Components: MP OpenAPI Reporter: Martin Svehla Assignee: Paul Ferraro Currently no validation is provided for generated document and actually the spec is not requesting for vendors to do that [1] but it would definitely be a key improvement for customers and users in general to know that the generated document is checked and appropriate action is taken in case content is not valid (e.g.: log WARN messages etc.). Online Swagger Editor [2] was used to verify that non valid content was generated. Also it should be evaluated whether to mention this behavior in community or product docs. [1] https://download.eclipse.org/microprofile/microprofile-open-api-1.1.2/mic... [2] https://editor.swagger.io/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 January 2020