October 2019 - jboss-jira - Jboss List Archives

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

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12486?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12486: ----------------------------------------- [~ehugonnet] FYI. > Memory leak in OpenTracing when deployment is redeployed multiple times > ----------------------------------------------------------------------- > > Key: WFLY-12486 > URL: https://issues.jboss.org/browse/WFLY-12486 > Project: WildFly > Issue Type: Bug > Components: MP OpenTracing > Affects Versions: 17.0.0.Final, 17.0.1.Final > Reporter: Jan Stourac > Assignee: Jeff Mesnil > Priority: Critical > Attachments: memory-leak-bad.png, memory-leak-good.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

1
0
0 / 0

[JBoss JIRA] (WFLY-12720) [18.0.1] Update BouncyCastle from 1.60 to 1.64

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12720?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12720: ----------------------------------------- https://nvd.nist.gov/vuln/detail/CVE-2019-17359 was a driver for this upgrade, but it actually didn't affect WildFly 18 as we were on 1.60 and the flaw was introduced in 1.63. We already upgraded master to 1.64 anyway, and I see no reason to roll the back. I'll have to give some thought to 18.0.1 though as we're generally quite conservative about changes in micros, and this CVE was the driver for making that change. > [18.0.1] Update BouncyCastle from 1.60 to 1.64 > ---------------------------------------------- > > Key: WFLY-12720 > URL: https://issues.jboss.org/browse/WFLY-12720 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.1.Final > > > Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12662) Update BouncyCastle from 1.60 to 1.64

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12662?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12662: ----------------------------------------- https://nvd.nist.gov/vuln/detail/CVE-2019-17359 actually didn't affect WildFly as we were on 1.60 and the flaw was introduced in 1.63. > Update BouncyCastle from 1.60 to 1.64 > ------------------------------------- > > Key: WFLY-12662 > URL: https://issues.jboss.org/browse/WFLY-12662 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > Fix For: 19.0.0.Beta1 > > > Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12720) [18.0.1] Update BouncyCastle from 1.60 to 1.64

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12720?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12720: --------------------------------------- Assignee: Brian Stansberry (was: Rostislav Svoboda) > [18.0.1] Update BouncyCastle from 1.60 to 1.64 > ---------------------------------------------- > > Key: WFLY-12720 > URL: https://issues.jboss.org/browse/WFLY-12720 > Project: WildFly > Issue Type: Task > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.1.Final > > > Update BouncyCastle -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12722) Upgrade Infinispan to 10.0.0.Final

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12722: ----------------------------------- Summary: Upgrade Infinispan to 10.0.0.Final Key: WFLY-12722 URL: https://issues.jboss.org/browse/WFLY-12722 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro https://issues.jboss.org/projects/ISPN/versions/12332894 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12694) Update jackson-databind to 2.9.10.1

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-12694?page=com.atlassian.jira.plugin... ] Alessio Soldano commented on WFLY-12694: ---------------------------------------- +1 , let's upgrade > Update jackson-databind to 2.9.10.1 > ----------------------------------- > > Key: WFLY-12694 > URL: https://issues.jboss.org/browse/WFLY-12694 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Rostislav Svoboda > Assignee: Rostislav Svoboda > Priority: Major > Fix For: 19.0.0.Beta1 > > > Update jackson-databind to 2.9.10.1 > https://github.com/FasterXML/jackson-databind/releases -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12721) [18.0.x] Upgrade commons-codec from 1.11 to 1.13

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12721: --------------------------------------- Summary: [18.0.x] Upgrade commons-codec from 1.11 to 1.13 Key: WFLY-12721 URL: https://issues.jboss.org/browse/WFLY-12721 Project: WildFly Issue Type: Component Upgrade Components: REST, Web Services Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 19.0.0.Beta1 Pull in updated commons-codec https://github.com/apache/commons-codec/compare/commons-codec-1.11...comm... https://commons.apache.org/proper/commons-codec/changes-report.html#a1.13 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12721) [18.0.x] Upgrade commons-codec from 1.11 to 1.13

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12721?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12721: ------------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12735) > [18.0.x] Upgrade commons-codec from 1.11 to 1.13 > ------------------------------------------------ > > Key: WFLY-12721 > URL: https://issues.jboss.org/browse/WFLY-12721 > Project: WildFly > Issue Type: Component Upgrade > Components: REST, Web Services > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.1.Final > > > Pull in updated commons-codec > https://github.com/apache/commons-codec/compare/commons-codec-1.11...comm... > https://commons.apache.org/proper/commons-codec/changes-report.html#a1.13 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12721) [18.0.x] Upgrade commons-codec from 1.11 to 1.13

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12721?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12721: ------------------------------------ Fix Version/s: 18.0.1.Final (was: 19.0.0.Beta1) > [18.0.x] Upgrade commons-codec from 1.11 to 1.13 > ------------------------------------------------ > > Key: WFLY-12721 > URL: https://issues.jboss.org/browse/WFLY-12721 > Project: WildFly > Issue Type: Component Upgrade > Components: REST, Web Services > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 18.0.1.Final > > > Pull in updated commons-codec > https://github.com/apache/commons-codec/compare/commons-codec-1.11...comm... > https://commons.apache.org/proper/commons-codec/changes-report.html#a1.13 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12653) Session passivation event can deadlock if it attempts write operations on a session

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12653?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-12653: ------------------------------------- [~brian.stansberry] Honestly, it should probably have been filed as critical. If you're ok with it going into 18.0.1, I would say yes. > Session passivation event can deadlock if it attempts write operations on a session > ----------------------------------------------------------------------------------- > > Key: WFLY-12653 > URL: https://issues.jboss.org/browse/WFLY-12653 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Labels: downstream_dependency > Fix For: 19.0.0.Beta1 > > > Activation/passivation listeners are intentionally non-transactional - and thus should never attempt to perform cache writes. > In order to trigger the requisite activation/passivation listeners, activation/passivation events need to lookup the cache entries relevant to a given session via SessionFactory.findValue(..). However, if there are entries missing (e.g. a creation meta data entry w/out a access meta data entry), this method will attempt to purge the orphaned entries. This should never be done within the context of an activation/passivation event. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019