February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-13779) MicroProfile Metrics tests started to fail since changes in ConfigSource

by Jason Lee (Jira)

[ https://issues.redhat.com/browse/WFLY-13779?page=com.atlassian.jira.plugi... ] Jason Lee commented on WFLY-13779: ---------------------------------- For the record, this is still an issue even when using the MicroProfile 4 branch. > MicroProfile Metrics tests started to fail since changes in ConfigSource > ------------------------------------------------------------------------ > > Key: WFLY-13779 > URL: https://issues.redhat.com/browse/WFLY-13779 > Project: WildFly > Issue Type: Bug > Components: MP Metrics > Reporter: Sultan Zhantemirov > Assignee: Jason Lee > Priority: Major > > WildFly build: 21.0.0.Beta1-SNAPSHOT > Java: oracle-java-11 > A several failures appeared in our small standalone test suite [1] for MicroProfile on WF/EAP. To be more specific, a few failures in MP Metrics that have one common cause: > {noformat} > java.lang.RuntimeException: config.source.properties.path property not defined > {noformat} > caused by line [2]. > I have a reason to believe that this PR [3] could be reason of these failures. What should be done in this case? > Thank you. > [1] - https://github.com/jboss-eap-qe/eap-microprofile-test-suite/tree/master/m... > [2] - https://github.com/jboss-eap-qe/eap-microprofile-test-suite/blob/8b726042... > [3] - https://github.com/wildfly/wildfly/pull/13247 > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (AG-154) Connection leak when DB connection closed during transaction rollback

by Wojciech Kopciewicz (Jira)

[ https://issues.redhat.com/browse/AG-154?page=com.atlassian.jira.plugin.sy... ] Wojciech Kopciewicz commented on AG-154: ---------------------------------------- Hi [~lbarreiro] We are actually not stopping the application - it is running all the time. It is the DB that is being closed (e.g. for maintenance) during the transaction. We are using 4 connections to the DB on each instance of the service - with 100 you will probably need more time to reproduce this. We are using Hibernate - EntityManager is injected. > Connection leak when DB connection closed during transaction rollback > --------------------------------------------------------------------- > > Key: AG-154 > URL: https://issues.redhat.com/browse/AG-154 > Project: Agroal > Issue Type: Bug > Components: narayana, pool > Affects Versions: 1.9 > Reporter: Wojciech Kopciewicz > Assignee: Luis Barreiro > Priority: Critical > > We are using Quarkus 1.9.2 with Hibernate and Agroal to access PostgreSQL DB. > It looks like Agroal is leaking connections when connection is closed (somewhere) on the server side during transaction rollback. > The following log was observed: > Error trying to transactionRollback local transaction: This connection has been closed. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (JGRP-2145) UDP: investigate slow-down compared to TCP

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2145?page=com.atlassian.jira.plugin... ] Bela Ban edited comment on JGRP-2145 at 2/9/21 2:40 PM: -------------------------------------------------------- This should be fixed with the update to fibers (virtual threads). See http://belaban.blogspot.com/2020/07/double-your-performance-virtual-threa.... Needs to be verified. was (Author: belaban): This should be fixed with the update to fibers (virtual threads). See http://belaban.blogspot.com/2020/07/double-your-performance-virtual-threa... > UDP: investigate slow-down compared to TCP > ------------------------------------------ > > Key: JGRP-2145 > URL: https://issues.redhat.com/browse/JGRP-2145 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.3 > > > With IspnPerfTest, a UDP-based config is roughly 30% slower on cluster01-08 than a TCP-based config. Investigate why. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (JGRP-2145) UDP: investigate slow-down compared to TCP

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2145?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2145: -------------------------------- This should be fixed with the update to fibers (virtual threads). See http://belaban.blogspot.com/2020/07/double-your-performance-virtual-threa... > UDP: investigate slow-down compared to TCP > ------------------------------------------ > > Key: JGRP-2145 > URL: https://issues.redhat.com/browse/JGRP-2145 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.3 > > > With IspnPerfTest, a UDP-based config is roughly 30% slower on cluster01-08 than a TCP-based config. Investigate why. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14412) Messaging: Simplified configuration of connection to remote integrated messaging broker

by Brad Maxwell (Jira)

[ https://issues.redhat.com/browse/WFLY-14412?page=com.atlassian.jira.plugi... ] Brad Maxwell updated WFLY-14412: -------------------------------- Component/s: JMS Target Release: (was: 7.backlog.GA) Affects Version/s: 18.0.0.Final > Messaging: Simplified configuration of connection to remote integrated messaging broker > --------------------------------------------------------------------------------------- > > Key: WFLY-14412 > URL: https://issues.redhat.com/browse/WFLY-14412 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Affects Versions: 18.0.0.Final > Reporter: Petr Hostalek > Priority: Major > Labels: activemq, artemis, messaging > > EAP 7.2 introduced a simplified configuration of remote connections to the remote Artemis-based messaging broker. Connectors, connection factories and queues/topics may be configured directly in the {{messaging-activemq}} subsystem so that the messaging server configuration isn't required at all: > [https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...] > [https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...] > However that makes use of the {{remote-connector}}. > When connecting to the integrated messaging broker at the remote JBoss EAP instance, the most straightforward is to use the {{http-connector}}. > This type of connector can be also configured directly in the {{messaging-activemq}} subsystem, however it requires the {{endpoint}} attribute to reference the {{http-acceptor}} which is intended for inbound connections and requires the messaging server configuration. > But since we require only outbound connections to the remote instance there's no real use for the {{endpoint}} configuration here and there should be no need to have any messaging server configured. > Could the {{endpoint}} attribute be made optional, at least right at the {{messaging-activemq}} level? Or could this be solved another way? -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14412) Messaging: Simplified configuration of connection to remote integrated messaging broker

by Brad Maxwell (Jira)

[ https://issues.redhat.com/browse/WFLY-14412?page=com.atlassian.jira.plugi... ] Brad Maxwell moved JBEAP-20760 to WFLY-14412: --------------------------------------------- Key: WFLY-14412 (was: JBEAP-20760) Target Release: (was: 7.backlog.GA) Affects Version/s: (was: 7.3.0.GA) (was: 7.3.4.GA) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Project: WildFly (was: JBoss Enterprise Application Platform) > Messaging: Simplified configuration of connection to remote integrated messaging broker > --------------------------------------------------------------------------------------- > > Key: WFLY-14412 > URL: https://issues.redhat.com/browse/WFLY-14412 > Project: WildFly > Issue Type: Enhancement > Reporter: Petr Hostalek > Priority: Major > Labels: activemq, artemis, messaging > > EAP 7.2 introduced a simplified configuration of remote connections to the remote Artemis-based messaging broker. Connectors, connection factories and queues/topics may be configured directly in the {{messaging-activemq}} subsystem so that the messaging server configuration isn't required at all: > [https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...] > [https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...] > However that makes use of the {{remote-connector}}. > When connecting to the integrated messaging broker at the remote JBoss EAP instance, the most straightforward is to use the {{http-connector}}. > This type of connector can be also configured directly in the {{messaging-activemq}} subsystem, however it requires the {{endpoint}} attribute to reference the {{http-acceptor}} which is intended for inbound connections and requires the messaging server configuration. > But since we require only outbound connections to the remote instance there's no real use for the {{endpoint}} configuration here and there should be no need to have any messaging server configured. > Could the {{endpoint}} attribute be made optional, at least right at the {{messaging-activemq}} level? Or could this be solved another way? -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14365) Programmatic web authentication (HttpServletRequest.login()) does not trigger sso

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-14365?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFLY-14365: ------------------------------------ Fix Version/s: 23.0.0.Beta1 > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso > --------------------------------------------------------------------------------- > > Key: WFLY-14365 > URL: https://issues.redhat.com/browse/WFLY-14365 > Project: WildFly > Issue Type: Bug > Reporter: Ilia Vassilev > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 23.0.0.Beta1 > > > Programmatic web authentication (HttpServletRequest.login()) does not trigger sso (JSESSIONIDSSO does not get created) when using elytron/undertow. > This worked fine in EAP 6 (eap 5 too but it was a bit different as > HttpServletRequest.login() wasn't available at that time). -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5762) DRLX Research Spike

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5762?page=com.atlassian.jira.plug... ] Edoardo Vacchi resolved DROOLS-5762. ------------------------------------ Resolution: Done > DRLX Research Spike > ------------------- > > Key: DROOLS-5762 > URL: https://issues.redhat.com/browse/DROOLS-5762 > Project: Drools > Issue Type: Story > Components: core engine > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Create a revised version of the DRLX language, i.e. a revised DRL language for rules definition, with less edge cases, and a slightly different syntax. > Spec design will follow. This story is meant to deliver a small, first version of the language, just to kick off the project. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5997) Initial DRLX support

by Edoardo Vacchi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5997?page=com.atlassian.jira.plug... ] Edoardo Vacchi resolved DROOLS-5997. ------------------------------------ Resolution: Done > Initial DRLX support > -------------------- > > Key: DROOLS-5997 > URL: https://issues.redhat.com/browse/DROOLS-5997 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.49.0.Final > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > Fix For: 7.50.0.Final > > > Add initial DRLX support for simple rule definitions; translate into *Descrs -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1286) Kiali REST API - Add health filters

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1286: ------------------------------------- Summary: Kiali REST API - Add health filters Key: SWSQE-1286 URL: https://issues.redhat.com/browse/SWSQE-1286 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Currently health filters are not applied in list items in kiali_api. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 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 February 2021