March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-938) Embedded host controller doesn't support --admin-mode=false option

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-938?page=com.atlassian.jira.plugin... ] Petr Kremensky closed WFCORE-938. --------------------------------- Resolution: Won't Do > Embedded host controller doesn't support --admin-mode=false option > ------------------------------------------------------------------ > > Key: WFCORE-938 > URL: https://issues.jboss.org/browse/WFCORE-938 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Affects Versions: 2.0.0.Beta4 > Reporter: Petr Kremensky > Assignee: ehsavoie Hugonnet > Labels: domain-mode > > Embedded standalone instance supports two running modes depending on a value of admin-only option (true is default). > * *true* > ** only start services related to server administration > ** do not start other services or accept end user requests. > ** embedded instance will not be visible to remote management clients > * *false* > ** all services are started > ** embedded instance is visible to remote management clients (e.g. EAP can be configured via admin console) > Embedded host controller doesn't offer such a option and is started using --admin-only=true mode by default. Option to run embedded host controller instance with --admin-only=false should be available as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-938) Embedded host controller doesn't support --admin-mode=false option

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-938?page=com.atlassian.jira.plugin... ] Petr Kremensky commented on WFCORE-938: --------------------------------------- This request was raised while we process the EAP7-92, but since it's more than two years now and there doesn't seem to be a need for the feature, I'm going to close it. If there is ever need for this, EAP7 should be filed. Thanks for all the input here. > Embedded host controller doesn't support --admin-mode=false option > ------------------------------------------------------------------ > > Key: WFCORE-938 > URL: https://issues.jboss.org/browse/WFCORE-938 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Affects Versions: 2.0.0.Beta4 > Reporter: Petr Kremensky > Assignee: ehsavoie Hugonnet > Labels: domain-mode > > Embedded standalone instance supports two running modes depending on a value of admin-only option (true is default). > * *true* > ** only start services related to server administration > ** do not start other services or accept end user requests. > ** embedded instance will not be visible to remote management clients > * *false* > ** all services are started > ** embedded instance is visible to remote management clients (e.g. EAP can be configured via admin console) > Embedded host controller doesn't offer such a option and is started using --admin-only=true mode by default. Option to run embedded host controller instance with --admin-only=false should be available as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2394) [DMN Designer] Rename of output changes back to link

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2394?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2394: -------------------------------- Description: Renaming output of decision table changes the {{back to}} link. h2. Acceptance tests # Three different decisions ## In DRD declare three different decision (different names) ## Check navigation to properties of these decisions # One decision ## In DRD declare one decision ## For each context entry type check ## Renaming in DRD -> also top level expression in properties renamed ## Renaming in decision properties -> also name in DRD changed ## Change of expression type preserves name ## Undo / Redo changes name both in properties and drd diagram ## In any moment diagram can be saved , closed and reopened was:Renaming output of decision table changes the {{back to}} link. > [DMN Designer] Rename of output changes back to link > ---------------------------------------------------- > > Key: DROOLS-2394 > URL: https://issues.jboss.org/browse/DROOLS-2394 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.7.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Optional > Attachments: Screenshot from 2018-03-16 12-14-13.png > > > Renaming output of decision table changes the {{back to}} link. > h2. Acceptance tests > # Three different decisions > ## In DRD declare three different decision (different names) > ## Check navigation to properties of these decisions > # One decision > ## In DRD declare one decision > ## For each context entry type check > ## Renaming in DRD -> also top level expression in properties renamed > ## Renaming in decision properties -> also name in DRD changed > ## Change of expression type preserves name > ## Undo / Redo changes name both in properties and drd diagram > ## In any moment diagram can be saved , closed and reopened -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10086) (7.1.z) Remove all slf4j dependencies from WildFly (EAP full)

by Lin Gao (JIRA)

Lin Gao created WFLY-10086: ------------------------------ Summary: (7.1.z) Remove all slf4j dependencies from WildFly (EAP full) Key: WFLY-10086 URL: https://issues.jboss.org/browse/WFLY-10086 Project: WildFly Issue Type: Task Components: Build System Affects Versions: 12.0.0.Final Reporter: Lin Gao Assignee: Jeff Mesnil Most of SLF4J dependencies are defined are in wildfly-core except for slf4j-ext. There are also transitive dependencies to jcl-over-slf4j for the JMS client BoM that requires to specify the version of SL4F in wildfly. The goal of this task is to move all SLF4J dependencies in wildlfy-core that will be the only and authoritative location to specify the version of SLF4J used in WildFly app server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3708) (7.1.z) Move all slf4j modules to WildFly Core eap

by Lin Gao (JIRA)

Lin Gao created WFCORE-3708: ------------------------------- Summary: (7.1.z) Move all slf4j modules to WildFly Core eap Key: WFCORE-3708 URL: https://issues.jboss.org/browse/WFCORE-3708 Project: WildFly Core Issue Type: Task Components: Server Reporter: Lin Gao Assignee: Jeff Mesnil Most of SLF4J dependencies are defined are in wildfly-core except for slf4j-ext. There are also transitive dependencies to jcl-over-slf4j for the JMS client BoM that requires to specify the version of SL4F in wildfly. The goal of this task is to move all SLF4J dependencies in wildlfy-core that will be the only and authoritative location to specify the version of SLF4J used in WildFly app server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10069) Remove all slf4j dependencies from WildFly

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFLY-10069?page=com.atlassian.jira.plugin... ] Lin Gao updated WFLY-10069: --------------------------- Labels: downstream_dependency (was: ) > Remove all slf4j dependencies from WildFly > ------------------------------------------ > > Key: WFLY-10069 > URL: https://issues.jboss.org/browse/WFLY-10069 > Project: WildFly > Issue Type: Task > Components: Build System > Affects Versions: 12.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Labels: downstream_dependency > > Most of SLF4J dependencies are defined are in wildfly-core except for slf4j-ext. > There are also transitive dependencies to jcl-over-slf4j for the JMS client BoM that requires to specify the version of SL4F in wildfly. > The goal of this task is to move all SLF4J dependencies in wildlfy-core that will be the only and authoritative location to specify the version of SLF4J used in WildFly app server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3703) Move all slf4j modules to WildFly Core

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3703?page=com.atlassian.jira.plugi... ] Lin Gao updated WFCORE-3703: ---------------------------- Labels: downstream_dependency (was: ) > Move all slf4j modules to WildFly Core > -------------------------------------- > > Key: WFCORE-3703 > URL: https://issues.jboss.org/browse/WFCORE-3703 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Labels: downstream_dependency > > Most of SLF4J dependencies are defined are in wildfly-core except for slf4j-ext. > There are also transitive dependencies to jcl-over-slf4j for the JMS client BoM that requires to specify the version of SL4F in wildfly. > The goal of this task is to move all SLF4J dependencies in wildlfy-core that will be the only and authoritative location to specify the version of SLF4J used in WildFly app server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10084) Add support for the proxy protocol

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-10084: ------------------------------------- Summary: Add support for the proxy protocol Key: WFLY-10084 URL: https://issues.jboss.org/browse/WFLY-10084 Project: WildFly Issue Type: Feature Request Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10085) Add support for the proxy protocol

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-10085: ------------------------------------- Summary: Add support for the proxy protocol Key: WFLY-10085 URL: https://issues.jboss.org/browse/WFLY-10085 Project: WildFly Issue Type: Feature Request Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9742) ClassLoader leak in JBoss Threads caused by MDBs

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9742?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-9742. ------------------------------------ Fix Version/s: 12.0.0.Final Resolution: Done WF 12 includes JBoss Threads 2.3.1, which has the related fix in it, so I'm marking this resolved in 12. It may have been resolved in CR1 or even Beta1 but I'm not going to research that. ;) > ClassLoader leak in JBoss Threads caused by MDBs > ------------------------------------------------ > > Key: WFLY-9742 > URL: https://issues.jboss.org/browse/WFLY-9742 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Final > Reporter: Markus Dlugi > Assignee: David Lloyd > Fix For: 12.0.0.Final > > Attachments: default-threads-tccl.png, jboss-threads-tccl-example.zip > > > There is a classloader leak in JBoss Threads which is most noticable when deploying MDBs. When a new MDB is created and a new thread for the MDB is started in the JCA thread pool ("default-threads - x"), the thread will be created using the context classloader of the MDB's deployment unit. This is because [MessageDrivenComponent.activate()|https://github.com/wildfly/wildfly/blob...] sets the context classloader of the ServerService thread in order to create the MDB, and this classloader will then also be used by the child thread. > In the default configuration, the threads in the default thread pool will not be terminated and therefore the thread will keep the reference to the classloader even when the deployment unit is undeployed. This in turn can lead to "OutOfMemoryError: Metaspace" after a couple of redeployments. > As a workaround, we changed [JBossThreadFactory.createThread()|https://github.com/jbossas/jboss-thread...] to set the context classloader to null after a new thread has been created. While this fixes the issue for us, I am not sure whether this is a good solution for all consumers of the thread factory, or if this should be fixed in the JCA subsystem instead. That's also the reason why I opened this issue against the WildFly project instead of JBoss Threads. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 March 2018