February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-4567) [DMN Designer] Can not save data type entry that ends up with white space

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4567?page=com.atlassian.jira.plug... ] Jozef Marko closed DROOLS-4567. ------------------------------- Resolution: Out of Date > [DMN Designer] Can not save data type entry that ends up with white space > ------------------------------------------------------------------------- > > Key: DROOLS-4567 > URL: https://issues.redhat.com/browse/DROOLS-4567 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.28.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2019-09-26 15-01-45.png > > > In the attachment is a situation of a user that wants to save a data type entry that ends with white space character. It is not easy to see but there is "memory " not just "memory". Now if user press the "Save" button no action is taken nor data type entry is saved. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6034) Unable to build project inserting and updating a fact of same rule running with an executable model

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-6034?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-6034: -------------------------------- Tester: Daniel Rosa (was: Jozef Marko) > Unable to build project inserting and updating a fact of same rule running with an executable model > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-6034 > URL: https://issues.redhat.com/browse/DROOLS-6034 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Attachments: RuleIssue_02864136.zip, pom.xml > > > Customer has rule which look like as: > > ~~~ > rule "Testrule" > dialect "mvel" > when > then > com.Employee e = new Employee(); > e.setId("1"); > insert( e ); > e.setName("abc"); > update( e ); > end > ~~~ > > If we try to build project it fails with below exception: > ~~~ > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel (default-generateModel) on project RuleIssue_02864136: Execution default-generateModel of goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel failed.: RuntimeException -> [Help 1] > [ERROR] > ~~~ > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

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

by Luis Barreiro (Jira)

[ https://issues.redhat.com/browse/AG-154?page=com.atlassian.jira.plugin.sy... ] Luis Barreiro resolved AG-154. ------------------------------ Fix Version/s: 1.10 Resolution: Done > 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 > Fix For: 1.10 > > > 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, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14443) Upgrade Mojarra to 3.0.0.SP04 in the EE9 feature pack

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-14443?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-14443: ------------------------------------ Labels: EE9 (was: ) > Upgrade Mojarra to 3.0.0.SP04 in the EE9 feature pack > ----------------------------------------------------- > > Key: WFLY-14443 > URL: https://issues.redhat.com/browse/WFLY-14443 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Labels: EE9 > > This upgrade incorporates fixes from the Mojarra 2.3.14.SP branch and is based off the upstream 3.0.0 tag. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-13940) SingletonDeploymentJBossAllTestCase fails intermittently in CI

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13940?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13940: -------------------------------- Summary: SingletonDeploymentJBossAllTestCase fails intermittently in CI (was: SingletonDeploymentJBossAllTestCase fails frequently in CI) > SingletonDeploymentJBossAllTestCase fails intermittently in CI > -------------------------------------------------------------- > > Key: WFLY-13940 > URL: https://issues.redhat.com/browse/WFLY-13940 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 21.0.0.Beta1, 22.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 23.0.0.Beta1 > > > https://ci.wildfly.org/project.html?projectId=WF_PullRequest&buildTypeId=... -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14441) Currency ProtoStream marshaller needs to tolerate locales with no default currency

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-14441?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-14441: -------------------------------- Description: or where default currency cannot be determined. See: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Cu... This was discovered via Weld's CI: https://github.com/weld/core/suites/2049777383/artifacts/41289426 was: or where default currency cannot be determined. See: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Cu... > Currency ProtoStream marshaller needs to tolerate locales with no default currency > ---------------------------------------------------------------------------------- > > Key: WFLY-14441 > URL: https://issues.redhat.com/browse/WFLY-14441 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 23.0.0.Beta1 > > > or where default currency cannot be determined. > See: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Cu... > This was discovered via Weld's CI: > https://github.com/weld/core/suites/2049777383/artifacts/41289426 -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14444) Reduce overhead of map protostream marshallers

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-14444?page=com.atlassian.jira.plugi... ] Paul Ferraro commented on WFLY-14444: ------------------------------------- Updated payload numbers are here: https://docs.google.com/spreadsheets/d/1f6FlXqxX7dYm44naHZfqLc5TjqlmscIdG... > Reduce overhead of map protostream marshallers > ---------------------------------------------- > > Key: WFLY-14444 > URL: https://issues.redhat.com/browse/WFLY-14444 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > We can reduce the overhead of map marshalling by marshalling key and value as separate repeated fields, rather than using a repeated Map.Entry field. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14434) Heap usage continuously growing and exhausting available heap memory in production

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-14434?page=com.atlassian.jira.plugi... ] Paul Ferraro resolved WFLY-14434. --------------------------------- Resolution: Out of Date [~manas.java] I'm going to close this JIRA as out-of-date. If you can demonstrate that this issue is reproducible on WF22 (or the upcoming WF32 Beta), please re-open this. > Heap usage continuously growing and exhausting available heap memory in production > ---------------------------------------------------------------------------------- > > Key: WFLY-14434 > URL: https://issues.redhat.com/browse/WFLY-14434 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Manas Panda > Assignee: Paul Ferraro > Priority: Major > Attachments: Heap_Size_keeps_increasing.jpg, Heap_dump_analysis_1.jpg > > > # Problem description: > Critical issue of heap usage continuously growing and exhausting available heap memory in production. As you can see in below heap dump org.infinispan.container.impl.DefaultDataContainer is growing as the time passes and not garbage collected by GC. This increase in heap happening after upgrading from Wildfly 10.1 to Wildfly 18.0.1. There is no change in JDK in both cases ( Wildfly 10.1 and Wildfly 18.0.1). > 2. Web application environment > * OS: RHEL 7.5 > * Wildfly 18.0.1 > * JDK 1.8 > * Wildfly is being run in cluster mode > * Integrated with Keycloak 3.4.3 for SSO ( SAML) > * Enabled Wildfly clustering mode > * G1GC garbage collector used. And 20gigs of heap allocated ( -Xmx) > * Environment of Web App on Wildfly 10.1 is same ( except Wildfly 18) with same hardware > * Web application uses Spring web framework and security > 3. Heap dump analysis > * We have few web users logging in and every second and external application consuming few API’s exposed by same application. > * As you can see infinispan.container.impl.DefaultDataContainer Has already grown 14gigs. > * Please note that web application does not use infinispan directly. > * The heap does not grow in wildfly 10.1 and its normal ( garbage gets collected and size gets reduced after GC) > Please find the snapshot as attached. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-12854) Consider to allow non-resuable metrics of the same name in subdeployments

by Jason Lee (Jira)

[ https://issues.redhat.com/browse/WFLY-12854?page=com.atlassian.jira.plugi... ] Jason Lee commented on WFLY-12854: ---------------------------------- Do we have a reproducer we can attach to this issue? > Consider to allow non-resuable metrics of the same name in subdeployments > ------------------------------------------------------------------------- > > Key: WFLY-12854 > URL: https://issues.redhat.com/browse/WFLY-12854 > Project: WildFly > Issue Type: Feature Request > Components: MP Metrics > Reporter: Ivan Straka > Assignee: Jason Lee > Priority: Major > > If two method annotated to use MP Metrics have same name. In case of _Counters_ (example): > * They are reusable there is actually one MP metric and both method invocation are counted to a single metric. > * They are non-reusable: > ** They are in the same deployment - ERROR is logged and metrics are not registerd > ** They are in different deployments > *** (X) MP Config _mp.metrics.appName_ is used thus metrics are registered under _configured_name;_app=the value_ thus they are registered under different name > *** MP Config _mp.metrics.appName_ is not used - ERROR is logged and metrics are not registerd > Now I'd like to talk about the (X) option. This is valid for two scenarios: > * Multiple deployments > * Deployment with sub-deployments. > In Multiple deployments I am able to to annotate two methods with non-reusable metric of the same name. I need to set MP Config _mp.metrics.appName_ property. Then I can select the metric using a tag. > However per https://github.com/smallrye/smallrye-metrics/issues/216 I am not able to do that in deployment with sub-deployments scenario. > This is inconsistent behavior and it would be good to have it implemented. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14101) signature test failures in jakarta.faces.view.facelets

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-14101?page=com.atlassian.jira.plugi... ] Scott Marlow resolved WFLY-14101. --------------------------------- Resolution: Done I think that this was resolved already so marking it as resolved. Thanks [~fjuma] > signature test failures in jakarta.faces.view.facelets > ------------------------------------------------------ > > Key: WFLY-14101 > URL: https://issues.redhat.com/browse/WFLY-14101 > Project: WildFly > Issue Type: Sub-task > Components: JSF > Reporter: Scott Marlow > Assignee: Farah Juma > Priority: Major > Labels: EE9 > > {quote} > Missing Methods > [javatest.batch] --------------- > [javatest.batch] > [javatest.batch] jakarta.faces.view.facelets.FaceletContext: method public java.lang.Object jakarta.el.ELContext.getContext(java.lang.Class<?>) > [javatest.batch] jakarta.faces.view.facelets.FaceletContext: method public void jakarta.el.ELContext.putContext(java.lang.Class<?>,java.lang.Object) > [javatest.batch] > [javatest.batch] Added Methods > [javatest.batch] ------------- > [javatest.batch] > [javatest.batch] jakarta.faces.view.facelets.FaceletContext: method public java.lang.Object jakarta.el.ELContext.getContext(java.lang.Class) > [javatest.batch] jakarta.faces.view.facelets.FaceletContext: method public void jakarta.el.ELContext.putContext(java.lang.Class,java.lang.Object) > {quote} -- This message was sent by Atlassian Jira (v8.13.1#813001)

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