June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13556) Memory leak in FlashScope - expired elements are not cleared

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13556?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13556: ------------------------------ Labels: (was: regression) > Memory leak in FlashScope - expired elements are not cleared > ------------------------------------------------------------ > > Key: WFLY-13556 > URL: https://issues.redhat.com/browse/WFLY-13556 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Farah Juma > Assignee: Bartosz Spyrko-Smietanko > Priority: Major > > *This is a regression agains the 7.2.z stream.* > Objects in FlashScope is not cleared and keep accumulating even if POST-REDIRECT-BACK is completed. > If we put a huge object to FlashScope continuously as the following code, Java heap space will be exhausted soon. > {code:java} > @Model > public class Action { > private static final int oneHundredMB = 1024 * 1024 * 100; > public String next() { > Flash flash = FacesContext.getCurrentInstance().getExternalContext().getFlash(); > flash.putNow("huge", new byte[oneHundredMB]); > return "index.xhtml?faces-redirect=true"; > } > } > {code} > When OutOfMemoryError is happened, flashInnerMap field in com.sun.faces.context.flash.ELFlash is bloated. > {noformat} > Class Name | Ref. Objects | Shallow Heap | Ref. Shallow Heap | Retained Heap > ----------------------------------------------------------------------------------------------------------------------------------------- > java.lang.Thread @ 0xeea24380 default task-1 Thread | 1 | 120 | 64 | 20,800 > '- <Java Local> com.sun.faces.context.flash.ELFlash @ 0xee9e4608 | 1 | 40 | 64 | 64 > '- flashInnerMap java.util.concurrent.ConcurrentHashMap @ 0xee9e4630| 1 | 64 | 64 | 314,574,048 > ----------------------------------------------------------------------------------------------------------------------------------------- > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13556) Memory leak in FlashScope - expired elements are not cleared

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13556?page=com.atlassian.jira.plugi... ] Farah Juma updated WFLY-13556: ------------------------------ Priority: Major (was: Critical) > Memory leak in FlashScope - expired elements are not cleared > ------------------------------------------------------------ > > Key: WFLY-13556 > URL: https://issues.redhat.com/browse/WFLY-13556 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Farah Juma > Assignee: Bartosz Spyrko-Smietanko > Priority: Major > Labels: regression > > *This is a regression agains the 7.2.z stream.* > Objects in FlashScope is not cleared and keep accumulating even if POST-REDIRECT-BACK is completed. > If we put a huge object to FlashScope continuously as the following code, Java heap space will be exhausted soon. > {code:java} > @Model > public class Action { > private static final int oneHundredMB = 1024 * 1024 * 100; > public String next() { > Flash flash = FacesContext.getCurrentInstance().getExternalContext().getFlash(); > flash.putNow("huge", new byte[oneHundredMB]); > return "index.xhtml?faces-redirect=true"; > } > } > {code} > When OutOfMemoryError is happened, flashInnerMap field in com.sun.faces.context.flash.ELFlash is bloated. > {noformat} > Class Name | Ref. Objects | Shallow Heap | Ref. Shallow Heap | Retained Heap > ----------------------------------------------------------------------------------------------------------------------------------------- > java.lang.Thread @ 0xeea24380 default task-1 Thread | 1 | 120 | 64 | 20,800 > '- <Java Local> com.sun.faces.context.flash.ELFlash @ 0xee9e4608 | 1 | 40 | 64 | 64 > '- flashInnerMap java.util.concurrent.ConcurrentHashMap @ 0xee9e4630| 1 | 64 | 64 | 314,574,048 > ----------------------------------------------------------------------------------------------------------------------------------------- > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13556) Memory leak in FlashScope - expired elements are not cleared

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/WFLY-13556?page=com.atlassian.jira.plugi... ] Farah Juma moved JBEAP-19628 to WFLY-13556: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13556 (was: JBEAP-19628) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JSF (was: JSF) Environment: (was: * JBoss EAP 7.2.3 (also JBoss EAP 7.1.6 that is the latest version in 7.1.x is affected by this issue)) Affects Version/s: (was: 7.3.1.CR1) QE Test Coverage: (was: +) Fix Version/s: (was: 7.3.2.GA) > Memory leak in FlashScope - expired elements are not cleared > ------------------------------------------------------------ > > Key: WFLY-13556 > URL: https://issues.redhat.com/browse/WFLY-13556 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Farah Juma > Assignee: Bartosz Spyrko-Smietanko > Priority: Critical > Labels: regression > > *This is a regression agains the 7.2.z stream.* > Objects in FlashScope is not cleared and keep accumulating even if POST-REDIRECT-BACK is completed. > If we put a huge object to FlashScope continuously as the following code, Java heap space will be exhausted soon. > {code:java} > @Model > public class Action { > private static final int oneHundredMB = 1024 * 1024 * 100; > public String next() { > Flash flash = FacesContext.getCurrentInstance().getExternalContext().getFlash(); > flash.putNow("huge", new byte[oneHundredMB]); > return "index.xhtml?faces-redirect=true"; > } > } > {code} > When OutOfMemoryError is happened, flashInnerMap field in com.sun.faces.context.flash.ELFlash is bloated. > {noformat} > Class Name | Ref. Objects | Shallow Heap | Ref. Shallow Heap | Retained Heap > ----------------------------------------------------------------------------------------------------------------------------------------- > java.lang.Thread @ 0xeea24380 default task-1 Thread | 1 | 120 | 64 | 20,800 > '- <Java Local> com.sun.faces.context.flash.ELFlash @ 0xee9e4608 | 1 | 40 | 64 | 64 > '- flashInnerMap java.util.concurrent.ConcurrentHashMap @ 0xee9e4630| 1 | 64 | 64 | 314,574,048 > ----------------------------------------------------------------------------------------------------------------------------------------- > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1979) Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-1979?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on ELY-1979: --------------------------------------- The initial pull request has been merged but further issues have been found related to how these changes needed the build adjusting, the changes to the build will need reverting so this fix will need to be converted to use reflection instead. > Elytron needs to deal with JEPS 244 in the org.wildfly.security.ssl package > --------------------------------------------------------------------------- > > Key: ELY-1979 > URL: https://issues.redhat.com/browse/ELY-1979 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.12.0.Final > Reporter: Brian Stansberry > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.12.1.CR1 > > > JEPS 244, available in JDK 9 or later and in JDK 8 since the 251 release[1] has added new methods to some of the javax.net.ssl classes that elytron wraps in org.wildfly.security.ssl. But the elytron classes do not handle those new methods. I believe the relevant change is at [2] and updates the SSLEngine, SSLParameters and SSLSocket classes (plus various non-javax classes.) > If Elytron were to require 251 or later to build perhaps this could be a simple matter of adding new methods to the wrappers and calling the delegate, under the expectation that at runtime the wrapper methods would not be invoked in a JVM < 251. Or the wrappers could use reflection and throw a UOE if the methods are not available. > [1] https://www.oracle.com/technetwork/java/javase/8u251-relnotes-5972664.htm... > [2] https://hg.openjdk.java.net/jdk8u/jdk8u41/jdk/rev/b26b096d4c89 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5405) NPE removing a rule from KieBase

by dianle zhang (Jira)

dianle zhang created DROOLS-5405: ------------------------------------ Summary: NPE removing a rule from KieBase Key: DROOLS-5405 URL: https://issues.redhat.com/browse/DROOLS-5405 Project: Drools Issue Type: Bug Components: build, core engine Affects Versions: 7.37.0.Final Reporter: dianle zhang Assignee: Ant Stephenson removing a rule from KieBase causes the following NPE: java.lang.NullPointerException: null at org.drools.core.phreak.AddRemoveRule.iterateLeftTuple(AddRemoveRule.java:1063) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.phreak.AddRemoveRule.visitChild(AddRemoveRule.java:978) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.phreak.AddRemoveRule.lambda$processLeftTuplesOnLian$1(AddRemoveRule.java:936) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.common.DefaultFactHandle$SingleLinkedTuples.forEachLeftTuple(DefaultFactHandle.java:727) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.common.DefaultFactHandle.forEachLeftTuple(DefaultFactHandle.java:923) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.phreak.AddRemoveRule.processLeftTuplesOnLian(AddRemoveRule.java:931) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.phreak.AddRemoveRule.processLeftTuples(AddRemoveRule.java:856) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.phreak.AddRemoveRule.removeRule(AddRemoveRule.java:173) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.reteoo.ReteooBuilder.removeTerminalNode(ReteooBuilder.java:191) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.reteoo.ReteooBuilder.removeRules(ReteooBuilder.java:177) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.impl.KnowledgeBaseImpl.lambda$removeRule$6(KnowledgeBaseImpl.java:1553) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.impl.KnowledgeBaseImpl.enqueueModification(KnowledgeBaseImpl.java:745) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1537) ~[drools-core-7.37.0.Final.jar:7.37.0.Final] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13555) Upgrade jgroups-azure to 1.3.0.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13555?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13555: ---------------------------------- Description: Tracks latest azure client and jgroups releases. Changes https://github.com/jgroups-extras/jgroups-azure/compare/1.2.1.Final...1.3... was:Only resolves the non-secure repositories issue. > Upgrade jgroups-azure to 1.3.0.Final > ------------------------------------ > > Key: WFLY-13555 > URL: https://issues.redhat.com/browse/WFLY-13555 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 20.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Final > > > Tracks latest azure client and jgroups releases. > Changes > https://github.com/jgroups-extras/jgroups-azure/compare/1.2.1.Final...1.3... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13555) Upgrade jgroups-azure to 1.3.0.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13555?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13555: ---------------------------------- Affects Version/s: 20.0.0.Beta1 (was: 16.0.0.Final) > Upgrade jgroups-azure to 1.3.0.Final > ------------------------------------ > > Key: WFLY-13555 > URL: https://issues.redhat.com/browse/WFLY-13555 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 20.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Final > > > Only resolves the non-secure repositories issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13555) Upgrade jgroups-azure to 1.3.0.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13555?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13555: ---------------------------------- Fix Version/s: 20.0.0.Final (was: 17.0.0.Alpha1) (was: 17.0.0.Final) > Upgrade jgroups-azure to 1.3.0.Final > ------------------------------------ > > Key: WFLY-13555 > URL: https://issues.redhat.com/browse/WFLY-13555 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 20.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Final > > > Only resolves the non-secure repositories issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13555) Upgrade jgroups-azure to 1.3.0.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13555?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13555: ---------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/12274) > Upgrade jgroups-azure to 1.3.0.Final > ------------------------------------ > > Key: WFLY-13555 > URL: https://issues.redhat.com/browse/WFLY-13555 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 20.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 20.0.0.Final > > > Only resolves the non-secure repositories issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13555) Upgrade jgroups-azure to 1.3.0.Final

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13555: ------------------------------------- Summary: Upgrade jgroups-azure to 1.3.0.Final Key: WFLY-13555 URL: https://issues.redhat.com/browse/WFLY-13555 Project: WildFly Issue Type: Component Upgrade Components: Clustering Affects Versions: 16.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 17.0.0.Alpha1, 17.0.0.Final Only resolves the non-secure repositories issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

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 June 2020