September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4521) Implement UI -> XML marshalling client side (Java/Js object -> xml)

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4521: ---------------------------------------- Summary: Implement UI -> XML marshalling client side (Java/Js object -> xml) Key: DROOLS-4521 URL: https://issues.jboss.org/browse/DROOLS-4521 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Implement/verify the marshalling (object -> xml) process client-side using JsInterop classes generated by gwt-jsonix plugin. Take equivalent server-side method as model. -- 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 Matěj Novotný (Jira)

[ https://issues.jboss.org/browse/WFLY-12446?page=com.atlassian.jira.plugin... ] Matěj Novotný commented on WFLY-12446: -------------------------------------- [~brian.stansberry] in CDI + EJB integration, all stateless beans are {{@Dependent}} from CDI perspective. And in this case there is {{Instance<X>}} used to resolve these dependent instances. In such case user is responsible for disposing them properly. So some of this logic should be there, not sure it's correct though, looking at it now. I am running the reproducer locally right now. > Memory leak in StatelessSessionComponent > ---------------------------------------- > > Key: WFLY-12446 > URL: https://issues.jboss.org/browse/WFLY-12446 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, EJB > Affects Versions: 17.0.1.Final > Reporter: Joerg Baesner > Assignee: Cheng Fang > Priority: Major > Attachments: dump-weld.png, playground-jee8.zip, server.log.gz, wfly-12446-heap-dump.png > > > 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] (WFCORE-4659) Partial revert of *not* having static default authentication context

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4659?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka updated WFCORE-4659: ------------------------------------- Summary: Partial revert of *not* having static default authentication context (was: Revert change of *not* having static default authentication context) > Partial revert of *not* having static default authentication context > -------------------------------------------------------------------- > > Key: WFCORE-4659 > URL: https://issues.jboss.org/browse/WFCORE-4659 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Beta4, 10.0.0.Beta6 > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Blocker > > The definition of the default security context was removed to be static https://github.com/wildfly/wildfly-core/pull/3892/commits/4f34c962fec06e8... as it could cause defective behaviour. To quote Stuart: > {quote} > The 'standard' default is basically random, as it can vary based on what the first TCCL to access it is. > {quote} > But removing the static default authentication context makes troubles for the transaction recovery which does not have no authentication context specified. Recovery can use only global one and while it's a workaround to the real issue of recovery has not defined any, it was a working solution. With the mentioned change this solution stopped to work. > Loading of the static authentication context should be reverted back and later fix properly. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12408) Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.Final

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12408?page=com.atlassian.jira.plugin... ] Eduardo Martins updated WFLY-12408: ----------------------------------- Summary: Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.Final (was: Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.CR1) > Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.Final > ---------------------------------------------------------------------- > > Key: WFLY-12408 > URL: https://issues.jboss.org/browse/WFLY-12408 > Project: WildFly > Issue Type: Sub-task > Components: Concurrency Utilities > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 18.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12408) Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.CR1

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12408?page=com.atlassian.jira.plugin... ] Eduardo Martins reopened WFLY-12408: ------------------------------------ re-opening for 2.0.0.Final > Upgrade jboss-concurrency-api_1.0_spec from 1.0.2.Final to 2.0.0.CR1 > -------------------------------------------------------------------- > > Key: WFLY-12408 > URL: https://issues.jboss.org/browse/WFLY-12408 > Project: WildFly > Issue Type: Sub-task > Components: Concurrency Utilities > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 18.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4515) Double word of service in the thrown exception ServiceNotFoundException

by Katarina Hermanova (Jira)

[ https://issues.jboss.org/browse/WFCORE-4515?page=com.atlassian.jira.plugi... ] Katarina Hermanova reassigned WFCORE-4515: ------------------------------------------ Assignee: Katarina Hermanova > Double word of service in the thrown exception ServiceNotFoundException > ----------------------------------------------------------------------- > > Key: WFCORE-4515 > URL: https://issues.jboss.org/browse/WFCORE-4515 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Vratislav Marek > Assignee: Katarina Hermanova > Priority: Minor > > The exception has in message double word service. > {code} > org.jboss.msc.service.ServiceNotFoundException: Service service org.wildfly.security.certificate-authority-account.FakeCaAccount not found > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4659) Revert change of *not* having static default authentication context

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created WFCORE-4659: ---------------------------------------- Summary: Revert change of *not* having static default authentication context Key: WFCORE-4659 URL: https://issues.jboss.org/browse/WFCORE-4659 Project: WildFly Core Issue Type: Bug Components: Security Affects Versions: 10.0.0.Beta6, 10.0.0.Beta4 Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka The definition of the default security context was removed to be static https://github.com/wildfly/wildfly-core/pull/3892/commits/4f34c962fec06e8... as it could cause defective behaviour. To quote Stuart: {quote} The 'standard' default is basically random, as it can vary based on what the first TCCL to access it is. {quote} But removing the static default authentication context makes troubles for the transaction recovery which does not have no authentication context specified. Recovery can use only global one and while it's a workaround to the real issue of recovery has not defined any, it was a working solution. With the mentioned change this solution stopped to work. Loading of the static authentication context should be reverted back and later fix properly. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4067) Add before/afterNodeEvaluated to enable monitoring of engine performance

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4067?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4067: -------------------------------- Sprint: 2019 Week 23-25, 2019 Week 38-40 (was: 2019 Week 23-25, 2019 Week 35-37) > Add before/afterNodeEvaluated to enable monitoring of engine performance > ------------------------------------------------------------------------ > > Key: DROOLS-4067 > URL: https://issues.jboss.org/browse/DROOLS-4067 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-186) PVC access mode is hardcoded to ReadWriteOnce

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-186?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFWIP-186: ----------------------------------- The StorageSpec is to mount the volume used to store the standalone/data dir. Was is ever supported to share this directory between pods? > PVC access mode is hardcoded to ReadWriteOnce > --------------------------------------------- > > Key: WFWIP-186 > URL: https://issues.jboss.org/browse/WFWIP-186 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > > Setting different access mode (ReadWriteMany, ReadOnlyMany) is ignored > [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-186) PVC access mode is hardcoded to ReadWriteOnce

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-186?page=com.atlassian.jira.plugin.... ] Martin Choma edited comment on WFWIP-186 at 9/11/19 2:13 AM: ------------------------------------------------------------- So Operator will be missing feature of configuring shared storage between pods? User won't be able to configure access mode ReadWriteMany nor ReadOnlyMany? Do I understand correctly? was (Author: mchoma): So Operator will be missing feature of configuring shared storage between pods? User won't be able to share neither ReadWriteMany nor ReadOnlyMany? Do I understand correctly? > PVC access mode is hardcoded to ReadWriteOnce > --------------------------------------------- > > Key: WFWIP-186 > URL: https://issues.jboss.org/browse/WFWIP-186 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Blocker > > Setting different access mode (ReadWriteMany, ReadOnlyMany) is ignored > [1] https://github.com/wildfly/wildfly-operator/blob/master/pkg/controller/wi... -- 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 September 2019