October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3337) Logging resources shouldn't be allowed to removed if they are in-use

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3337?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFCORE-3337 at 10/6/17 12:05 PM: -------------------------------------------------------------------- Nope, capabilities don't have to expose services. Definitely if all the wiring between your resources was tracked via caps/reqs then you would get standard failure behavior if people tried to break model integrity. was (Author: brian.stansberry): Nope, capabilities don't have to expose services. > Logging resources shouldn't be allowed to removed if they are in-use > -------------------------------------------------------------------- > > Key: WFCORE-3337 > URL: https://issues.jboss.org/browse/WFCORE-3337 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > Currently you can remove a logging resource even if it's used by another resource. An example of this would be the ability to remove a formatter even though that formatter is attached to a handler. Removing handlers does validate it's not attached to a logger first. However all logging resources should do this. > Note that logging does not use services which is why this needs to be manually checked. This should be doable via the configuration API. Note too that a fix to validate this will also be done in the logmanager, LOGMGR-179. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3337) Logging resources shouldn't be allowed to removed if they are in-use

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3337?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3337: ------------------------------------------ Nope, capabilities don't have to expose services. > Logging resources shouldn't be allowed to removed if they are in-use > -------------------------------------------------------------------- > > Key: WFCORE-3337 > URL: https://issues.jboss.org/browse/WFCORE-3337 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > Currently you can remove a logging resource even if it's used by another resource. An example of this would be the ability to remove a formatter even though that formatter is attached to a handler. Removing handlers does validate it's not attached to a logger first. However all logging resources should do this. > Note that logging does not use services which is why this needs to be manually checked. This should be doable via the configuration API. Note too that a fix to validate this will also be done in the logmanager, LOGMGR-179. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3338) Management returning success for read-attribute on non-existent domain server path

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3338?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3338: ------------------------------------- Summary: Management returning success for read-attribute on non-existent domain server path (was: Management returning success for read-attribute on non-existent path) > Management returning success for read-attribute on non-existent domain server path > ---------------------------------------------------------------------------------- > > Key: WFCORE-3338 > URL: https://issues.jboss.org/browse/WFCORE-3338 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.4.Final > Reporter: Brad Maxwell > Assignee: ehsavoie Hugonnet > > In Wildfly, a command such as this with a non-existent path returns success instead of failed: > {code} > /host=master/server=nonExistant:read-attribute(name=runtime-configuration-state) > { > "outcome" => "success", > "result" => "stopped" > } > {code} > Where as in EAP 6.4: > {code} > [domain@localhost:9999 /] /host=master/server=server-NOT-EXIST:read-attribute(name=server-state) > Failed to get the list of the operation properties: "JBAS014883: No resource definition is registered for address [ > ("host" => "master"), > ("server" => "server-NOT-EXIST") > ]" > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3338) Management returning success for read-attribute on non-existent path

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3338?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3338: ---------------------------------------- Assignee: ehsavoie Hugonnet (was: Brian Stansberry) I believe the problem here is StoppedServerResource. For all the attributes it exposes the OSH needs to do a non-recursive read of the /host=x resource and check the names of the server-config resources. If the name of the server the op is targeting is not present there, the OSH should throw a NoSuchResource exception. Tests should be added, probably to ServerManagementTestCase. > Management returning success for read-attribute on non-existent path > -------------------------------------------------------------------- > > Key: WFCORE-3338 > URL: https://issues.jboss.org/browse/WFCORE-3338 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.4.Final > Reporter: Brad Maxwell > Assignee: ehsavoie Hugonnet > > In Wildfly, a command such as this with a non-existent path returns success instead of failed: > {code} > /host=master/server=nonExistant:read-attribute(name=runtime-configuration-state) > { > "outcome" => "success", > "result" => "stopped" > } > {code} > Where as in EAP 6.4: > {code} > [domain@localhost:9999 /] /host=master/server=server-NOT-EXIST:read-attribute(name=server-state) > Failed to get the list of the operation properties: "JBAS014883: No resource definition is registered for address [ > ("host" => "master"), > ("server" => "server-NOT-EXIST") > ]" > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1750) DroolsAuthoringPerspectiveActivity failed in OPEN (KIE Workbench 6.5.0)

by R D (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1750?page=com.atlassian.jira.plugi... ] R D commented on DROOLS-1750: ----------------------------- OK, thank you. The client I am working for at the moment has 6.5.0 installed so I cannot make the switch to 7.3.0, but I will keep this in mind. > DroolsAuthoringPerspectiveActivity failed in OPEN (KIE Workbench 6.5.0) > ----------------------------------------------------------------------- > > Key: DROOLS-1750 > URL: https://issues.jboss.org/browse/DROOLS-1750 > Project: Drools > Issue Type: Bug > Affects Versions: 6.5.0.Final > Environment: WildFly 10.1 > KIE Workbench 6.5.0 > Reporter: R D > Assignee: Edson Tirelli > Fix For: 7.3.0.Final > > Attachments: Captura.PNG > > > Ever since making visible the KIE execution server in the KIE workbench, I get an error when switchting to the Project Authoring (see attachment). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9422) Wildfly HTTP client 1.0.6.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9422?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-9422: --------------------------------- Summary: Wildfly HTTP client 1.0.6.Final (was: Wildfly HTTP client 1.0.5.Final) > Wildfly HTTP client 1.0.6.Final > ------------------------------- > > Key: WFLY-9422 > URL: https://issues.jboss.org/browse/WFLY-9422 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9422) Wildfly HTTP client 1.0.5.Final

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9422?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-13399 to WFLY-9422: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9422 (was: JBEAP-13399) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) > Wildfly HTTP client 1.0.5.Final > ------------------------------- > > Key: WFLY-9422 > URL: https://issues.jboss.org/browse/WFLY-9422 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3342) Upgrade JBoss Remoting to 5.0.3.Final

by David Lloyd (JIRA)

David Lloyd created WFCORE-3342: ----------------------------------- Summary: Upgrade JBoss Remoting to 5.0.3.Final Key: WFCORE-3342 URL: https://issues.jboss.org/browse/WFCORE-3342 Project: WildFly Core Issue Type: Component Upgrade Components: Remoting Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.5.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3341) Upgrade XNIO to 3.5.2.Final

by David Lloyd (JIRA)

David Lloyd created WFCORE-3341: ----------------------------------- Summary: Upgrade XNIO to 3.5.2.Final Key: WFCORE-3341 URL: https://issues.jboss.org/browse/WFCORE-3341 Project: WildFly Core Issue Type: Component Upgrade Components: IO Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.5.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3340) Upgrade JBoss Marshalling to 2.0.2.Final

by David Lloyd (JIRA)

David Lloyd created WFCORE-3340: ----------------------------------- Summary: Upgrade JBoss Marshalling to 2.0.2.Final Key: WFCORE-3340 URL: https://issues.jboss.org/browse/WFCORE-3340 Project: WildFly Core Issue Type: Component Upgrade Components: Remoting Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.5.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 October 2017