January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12486) Memory leak in OpenTracing when deployment is redeployed multiple times

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-12486?page=com.atlassian.jira.plugi... ] James Perkins updated WFLY-12486: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12836, https://github.com/wildfly/wildfly/pull/12878 (was: https://github.com/wildfly/wildfly/pull/12836) > Memory leak in OpenTracing when deployment is redeployed multiple times > ----------------------------------------------------------------------- > > Key: WFLY-12486 > URL: https://issues.redhat.com/browse/WFLY-12486 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 17.0.0.Final, 17.0.1.Final, 18.0.1.Final > Reporter: Jan Stourac > Assignee: Emmanuel Hugonnet > Priority: Blocker > Fix For: 19.0.0.Beta1 > > Attachments: memory-leak-bad.png, memory-leak-good.png, wildfly-thread-leak.png > > > There seems to be a memory leak when a deployment is redeployed multiple times (100 times in our test). This is very similar to what has been described in WFLY-10991. Also first commit this started to happen is [this one|https://github.com/wildfly/wildfly/commit/74170b5f49dd83f6b9ebd489f85...] - JaegerTracing and Apache Thrift dependencies update. Thus I selected MP OpenTracing component for this issue. > Test and deployment is same as is described in WFLY-10991. > Size of the extra heap in use is about 27MB plus when compared to the initial size before multiple redeploy operations. > I've tried to check manually via [visualVM|https://visualvm.github.io/] tool. Screenshot with suspicious jaegertracing instances are attached - there are much more jaegertracing class instances with new version of Jager Tracing and Apache Thrift dependencies, which is suspicious. > Interesting thing is that when microprofile-opentracing-smallrye subsystem is removed via: > {code} > /subsystem=microprofile-opentracing-smallrye:remove() > {code} > the memory leak is still present. This is kind of confusing to me. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12939) Local scheduler should trigger expiration *after* distributed web session/SFSB has expired.

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12939: ----------------------------------- Summary: Local scheduler should trigger expiration *after* distributed web session/SFSB has expired. Key: WFLY-12939 URL: https://issues.redhat.com/browse/WFLY-12939 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro The expiration scheduler schedules a task to expire a web sesssion/SFSB using the last modified time + the max inactive interval (or @StatefulTimeout). However, technically, the session/bean is not expired until after this time. This off-by-one bug can cause the expiration task to determine that the session is not yet expired and thus can result in delayed expiration of a session. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-86) Release Elytron Web 1.7.0.CR4

by Farah Juma (Jira)

Farah Juma created ELYWEB-86: -------------------------------- Summary: Release Elytron Web 1.7.0.CR4 Key: ELYWEB-86 URL: https://issues.redhat.com/browse/ELYWEB-86 Project: Elytron Web Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma Fix For: 1.7.0.CR4 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-85) Upgrade WildFly Elytron to 1.11.0.CR5

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELYWEB-85?page=com.atlassian.jira.plugin... ] Farah Juma updated ELYWEB-85: ----------------------------- Fix Version/s: 1.7.0.CR4 > Upgrade WildFly Elytron to 1.11.0.CR5 > ------------------------------------- > > Key: ELYWEB-85 > URL: https://issues.redhat.com/browse/ELYWEB-85 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.7.0.CR4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-85) Upgrade WildFly Elytron to 1.11.0.CR5

by Farah Juma (Jira)

Farah Juma created ELYWEB-85: -------------------------------- Summary: Upgrade WildFly Elytron to 1.11.0.CR5 Key: ELYWEB-85 URL: https://issues.redhat.com/browse/ELYWEB-85 Project: Elytron Web Issue Type: Component Upgrade Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1754) Update test for JDK cipher suites cover when TLS 1.3 support is added

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1754?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1754: ---------------------------- Fix Version/s: 1.11.0.CR5 > Update test for JDK cipher suites cover when TLS 1.3 support is added > --------------------------------------------------------------------- > > Key: ELY-1754 > URL: https://issues.redhat.com/browse/ELY-1754 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Diana Vilkolakova > Assignee: Farah Juma > Priority: Major > Fix For: 1.11.0.CR5 > > > Elytron testsuite contains test whether Mechanism Database covers all cipher suites from JDK. Currently we are excluding testing for cipher suites from TLS 1.3. After the support of TLS 1.3 is added, this test should be updated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1918) Release WildFly Elytron 1.11.0.CR5

by Farah Juma (Jira)

Farah Juma created ELY-1918: ------------------------------- Summary: Release WildFly Elytron 1.11.0.CR5 Key: ELY-1918 URL: https://issues.redhat.com/browse/ELY-1918 Project: WildFly Elytron Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma Fix For: 1.11.0.CR5 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12938) Expired distributed web sessions/SFSBs not properly removed following topology change with no rehash

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12938: ----------------------------------- Summary: Expired distributed web sessions/SFSBs not properly removed following topology change with no rehash Key: WFLY-12938 URL: https://issues.redhat.com/browse/WFLY-12938 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro On topology change, changes to primary session ownership determine when a given member should schedule expiration of a given session, or cancel a scheduled expiration of a previously owned session. Primary ownership is determined by 2 components: the key partitioner and a consistent hash. The key partitioner determines which the segment to which a given key is assigned. A consistent hash determines which member is the primary owner of a given segment. Rescheduling of session expiration is triggered from a data rehash event. However, when the second to last member leaves the cluster, there is no data rehash event, thus expired session owned by the leaving member are never removed. To fix this, we must also trigger rescheduling of expiration in the event of a topology change where no rehashing occurs. This results in expired web sessions/SFSBs remaining in memory, potentially indefinitely. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4907) DMN FunctionDefinition parameter not trimmed by editor

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4907?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-4907: ----------------------------------- Labels: drools-tools (was: ) > DMN FunctionDefinition parameter not trimmed by editor > ------------------------------------------------------ > > Key: DROOLS-4907 > URL: https://issues.redhat.com/browse/DROOLS-4907 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: image-2020-01-07-17-19-25-638.png > > > Parameter are not trimmed by the editor > !image-2020-01-07-17-19-25-638.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4907) DMN FunctionDefinition parameter not trimmed by editor

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4907?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-4907: ----------------------------------- Story Points: 3 Sprint: 2020 Week 01-03 (from Dec 30) > DMN FunctionDefinition parameter not trimmed by editor > ------------------------------------------------------ > > Key: DROOLS-4907 > URL: https://issues.redhat.com/browse/DROOLS-4907 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: image-2020-01-07-17-19-25-638.png > > > Parameter are not trimmed by the editor > !image-2020-01-07-17-19-25-638.png|thumbnail! -- 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