January 2020 - jboss-jira - Jboss List Archives

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

by Karel Suta (Jira)

Karel Suta created DROOLS-4927: ---------------------------------- Summary: 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: Maciej Swiderski 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12958) [GSS](7.3.z) Calling Asynchronous EJB will use the propagated caller transaction which is not according to the specification

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-12958?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-12958: ----------------------------------- See discussion in https://issues.redhat.com/browse/JBEAP-18371 > [GSS](7.3.z) Calling Asynchronous EJB will use the propagated caller transaction which is not according to the specification > ---------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12958 > URL: https://issues.redhat.com/browse/WFLY-12958 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Blocker > Labels: spec_violation > > Asynchronous Invocations are not supposed to be part of the callers transaction because there is no guarantee that the async call is executed in parallel or after the caller already ended. > This will cause warnings and exceptions if the asynchronous call is trying to use the transaction while the container is commiting or rolling back the transaction. > It will break compatibility when migrating from earlier version (<=7.0). > According to the EJB specification > ~~~quote > 4.5.3 Transactions > The client’s transaction context does not propagate with an asynchronous method invocation. From the > Bean Provider’s point of view, there is never a transaction context flowing in from the client. This > means, for example, that the semantics of the REQUIRED transaction attribute on an asynchronous > method are exactly the same as REQUIRES_NEW. > ~~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12958) [GSS](7.3.z) Calling Asynchronous EJB will use the propagated caller transaction which is not according to the specification

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-12958?page=com.atlassian.jira.plugi... ] Cheng Fang moved JBEAP-18452 to WFLY-12958: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12958 (was: JBEAP-18452) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB (was: EJB) Affects Version/s: (was: 7.1.5.GA) (was: 7.2.4.GA) > [GSS](7.3.z) Calling Asynchronous EJB will use the propagated caller transaction which is not according to the specification > ---------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12958 > URL: https://issues.redhat.com/browse/WFLY-12958 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Cheng Fang > Assignee: Panagiotis Sotiropoulos > Priority: Blocker > Labels: spec_violation > > Asynchronous Invocations are not supposed to be part of the callers transaction because there is no guarantee that the async call is executed in parallel or after the caller already ended. > This will cause warnings and exceptions if the asynchronous call is trying to use the transaction while the container is commiting or rolling back the transaction. > It will break compatibility when migrating from earlier version (<=7.0). > According to the EJB specification > ~~~quote > 4.5.3 Transactions > The client’s transaction context does not propagate with an asynchronous method invocation. From the > Bean Provider’s point of view, there is never a transaction context flowing in from the client. This > means, for example, that the semantics of the REQUIRED transaction attribute on an asynchronous > method are exactly the same as REQUIRES_NEW. > ~~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12958) [GSS](7.3.z) Calling Asynchronous EJB will use the propagated caller transaction which is not according to the specification

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-12958?page=com.atlassian.jira.plugi... ] Cheng Fang reassigned WFLY-12958: --------------------------------- Assignee: Cheng Fang (was: Panagiotis Sotiropoulos) > [GSS](7.3.z) Calling Asynchronous EJB will use the propagated caller transaction which is not according to the specification > ---------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12958 > URL: https://issues.redhat.com/browse/WFLY-12958 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Blocker > Labels: spec_violation > > Asynchronous Invocations are not supposed to be part of the callers transaction because there is no guarantee that the async call is executed in parallel or after the caller already ended. > This will cause warnings and exceptions if the asynchronous call is trying to use the transaction while the container is commiting or rolling back the transaction. > It will break compatibility when migrating from earlier version (<=7.0). > According to the EJB specification > ~~~quote > 4.5.3 Transactions > The client’s transaction context does not propagate with an asynchronous method invocation. From the > Bean Provider’s point of view, there is never a transaction context flowing in from the client. This > means, for example, that the semantics of the REQUIRED transaction attribute on an asynchronous > method are exactly the same as REQUIRES_NEW. > ~~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12875) Upgrade wildfly-http-client from 1.0.18 to 1.0.19

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12875?page=com.atlassian.jira.plugi... ] Ilia Vassilev resolved WFLY-12875. ---------------------------------- Resolution: Duplicate Issue Duplicate of WFLY-12949 > Upgrade wildfly-http-client from 1.0.18 to 1.0.19 > ------------------------------------------------- > > Key: WFLY-12875 > URL: https://issues.redhat.com/browse/WFLY-12875 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > > https://github.com/wildfly/wildfly-http-client -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12879) Upgrade jboss-ejb-client from 4.0.27.Final to 4.0.28.Final

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12879?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned WFLY-12879: ------------------------------------ Assignee: Ilia Vassilev (was: Tomasz Adamski) > Upgrade jboss-ejb-client from 4.0.27.Final to 4.0.28.Final > ---------------------------------------------------------- > > Key: WFLY-12879 > URL: https://issues.redhat.com/browse/WFLY-12879 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > https://github.com/wildfly/jboss-ejb-client -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12879) Upgrade jboss-ejb-client from 4.0.27.Final to 4.0.28.Final

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12879?page=com.atlassian.jira.plugi... ] Ilia Vassilev resolved WFLY-12879. ---------------------------------- Resolution: Duplicate Issue Duplicate of WFLY-12911 > Upgrade jboss-ejb-client from 4.0.27.Final to 4.0.28.Final > ---------------------------------------------------------- > > Key: WFLY-12879 > URL: https://issues.redhat.com/browse/WFLY-12879 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > https://github.com/wildfly/jboss-ejb-client -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4905) [DMN Designer] Code Completion - Index all elements named by users

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4905?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4905: ------------------------------------ Sprint: 2020 Week 01-03 (from Dec 30) > [DMN Designer] Code Completion - Index all elements named by users > ------------------------------------------------------------------ > > Key: DROOLS-4905 > URL: https://issues.redhat.com/browse/DROOLS-4905 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Create the infrastructure code that provided all elements named by the user. It will be called by the suggestion component. So users will be able to see as suggestions DRG Elements and Data Types. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12957) MP Fault tolerance tests are failing on Ubuntu

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-12957?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet updated WFLY-12957: ------------------------------------- Affects Version/s: 18.0.0.Beta1 > MP Fault tolerance tests are failing on Ubuntu > ---------------------------------------------- > > Key: WFLY-12957 > URL: https://issues.redhat.com/browse/WFLY-12957 > Project: WildFly > Issue Type: Bug > Components: MP Fault Tolerance, Test Suite > Affects Versions: 18.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > Environment variables with dots in their name are not supported on Ubuntu making the fault tolerance tests fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12957) MP Fault tolerance tests are failing on Ubuntu

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFLY-12957: ---------------------------------------- Summary: MP Fault tolerance tests are failing on Ubuntu Key: WFLY-12957 URL: https://issues.redhat.com/browse/WFLY-12957 Project: WildFly Issue Type: Bug Components: MP Fault Tolerance, Test Suite Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Environment variables with dots in their name are not supported on Ubuntu making the fault tolerance tests fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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