August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1765) Review authentication client dependencies on credential sources

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1765?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1765: ---------------------------- Fix Version/s: 1.10.0.CR7 (was: 1.10.0.CR6) > Review authentication client dependencies on credential sources > --------------------------------------------------------------- > > Key: ELY-1765 > URL: https://issues.jboss.org/browse/ELY-1765 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.10.0.CR7 > > > Could these credential sources be discoverable from java.security.Provider with a more generic configuration API? This could help break any dependency from authentication client to the implementation. > _In the opposite direction I think it is Ok for the impl to depend on the client._ -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1749) Code review of WildFlyElytronProvider

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1749?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1749: ---------------------------- Fix Version/s: 1.10.0.CR7 (was: 1.10.0.CR6) > Code review of WildFlyElytronProvider > ------------------------------------- > > Key: ELY-1749 > URL: https://issues.jboss.org/browse/ELY-1749 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.10.0.CR7 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1865) Release WildFly Elytron 1.10.0.CR6

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1865?page=com.atlassian.jira.plugin.s... ] Farah Juma resolved ELY-1865. ----------------------------- Fix Version/s: 1.10.0.CR6 Resolution: Done > Release WildFly Elytron 1.10.0.CR6 > ---------------------------------- > > Key: ELY-1865 > URL: https://issues.jboss.org/browse/ELY-1865 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.10.0.CR6 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4634) Upgrade WildFly Elytron to 1.10.0.CR6

by Farah Juma (Jira)

Farah Juma created WFCORE-4634: ---------------------------------- Summary: Upgrade WildFly Elytron to 1.10.0.CR6 Key: WFCORE-4634 URL: https://issues.jboss.org/browse/WFCORE-4634 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma Fix For: 10.0.0.Beta5 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1865) Release WildFly Elytron 1.10.0.CR6

by Farah Juma (Jira)

Farah Juma created ELY-1865: ------------------------------- Summary: Release WildFly Elytron 1.10.0.CR6 Key: ELY-1865 URL: https://issues.jboss.org/browse/ELY-1865 Project: WildFly Elytron Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12446) Memory leak in StatelessSessionComponent

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12446?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12446: ----------------------------------------- Note that that duplicate discard call problem would have the effect of slowly increasing the max size of the pool. It doesn't leak 'bad' beans into the pool though. So I believe the size of the queue would be limited to the max # of concurrent requests, so not a never ending leak. So perhaps that is not the cause of the reported problem. > Memory leak in StatelessSessionComponent > ---------------------------------------- > > Key: WFLY-12446 > URL: https://issues.jboss.org/browse/WFLY-12446 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 17.0.1.Final > Reporter: Joerg Baesner > Assignee: Cheng Fang > Priority: Major > Attachments: playground-jee8.zip > > > When running the attached reproducer application and doing a memory analysis afterwards, it looks like a memory leak, e. g. > {code} > One instance of "org.jboss.as.ejb3.component.stateless.StatelessSessionComponent" loaded by "org.jboss.modules.ModuleClassLoader @ 0x5e0fbc2e0" occupies 936,593,520 (96.13%) bytes. The memory is accumulated in one instance of "java.util.concurrent.ConcurrentLinkedQueue$Node" loaded by "<system class loader>". > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12446) Memory leak in StatelessSessionComponent

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12446?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12446: ----------------------------------------- Perhaps the problem is here: https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... combined with here: https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... The inner catch block discards and then the outer one discards again. Only one bean got removed from the pool (i.e. the StrictMaxPool.pool ConcurrentLinkedQueue) but the semaphore gets decremented twice. > Memory leak in StatelessSessionComponent > ---------------------------------------- > > Key: WFLY-12446 > URL: https://issues.jboss.org/browse/WFLY-12446 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 17.0.1.Final > Reporter: Joerg Baesner > Assignee: Cheng Fang > Priority: Major > Attachments: playground-jee8.zip > > > When running the attached reproducer application and doing a memory analysis afterwards, it looks like a memory leak, e. g. > {code} > One instance of "org.jboss.as.ejb3.component.stateless.StatelessSessionComponent" loaded by "org.jboss.modules.ModuleClassLoader @ 0x5e0fbc2e0" occupies 936,593,520 (96.13%) bytes. The memory is accumulated in one instance of "java.util.concurrent.ConcurrentLinkedQueue$Node" loaded by "<system class loader>". > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4477) [DMN Designer] Decision Services - When a decision service is deleted all associated decisions are also deleted

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4477?page=com.atlassian.jira.plugi... ] Guilherme Gomes reassigned DROOLS-4477: --------------------------------------- Assignee: Guilherme Gomes (was: Daniel José dos Santos) > [DMN Designer] Decision Services - When a decision service is deleted all associated decisions are also deleted > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4477 > URL: https://issues.jboss.org/browse/DROOLS-4477 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > When a decision service is deleted in the model, all associated decisions are deleted with it. The inner nodes shouldn't be deleted. > DMN Spec: “Decision services are defined as overlays and therefore do not encapsulate the decisions within them.“ (section 6.2.5, p44) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4477) [DMN Designer] Decision Services - When a decision service is deleted all associated decisions are also deleted

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4477?page=com.atlassian.jira.plugi... ] Guilherme Gomes reassigned DROOLS-4477: --------------------------------------- Assignee: Daniel José dos Santos (was: Guilherme Gomes) > [DMN Designer] Decision Services - When a decision service is deleted all associated decisions are also deleted > --------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4477 > URL: https://issues.jboss.org/browse/DROOLS-4477 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > When a decision service is deleted in the model, all associated decisions are deleted with it. The inner nodes shouldn't be deleted. > DMN Spec: “Decision services are defined as overlays and therefore do not encapsulate the decisions within them.“ (section 6.2.5, p44) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4309) [DMN Designer] Search feature - The cell is not highlighted/focused when GDT is on pinned mode

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4309?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4309: ------------------------------------ Sprint: 2019 Week 32-34 (was: 2019 Week 32-34, 2019 Week 35-37) > [DMN Designer] Search feature - The cell is not highlighted/focused when GDT is on pinned mode > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-4309 > URL: https://issues.jboss.org/browse/DROOLS-4309 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > When the GDT is on edit mode, the canvas does not move to show the highlighted a cell that's not visible. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 August 2019