October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3344) Upgrade WildFly Elytron to 1.1.4.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3344: ---------------------------------------- Summary: Upgrade WildFly Elytron to 1.1.4.Final Key: WFCORE-3344 URL: https://issues.jboss.org/browse/WFCORE-3344 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Blocker Fix For: 3.0.5.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3343) Upgrade WildFly Elytron to 1.1.4.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3343?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved JBEAP-13408 to WFCORE-3343: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3343 (was: JBEAP-13408) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) > Upgrade WildFly Elytron to 1.1.4.Final > -------------------------------------- > > Key: WFCORE-3343 > URL: https://issues.jboss.org/browse/WFCORE-3343 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.5.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3333) Expose number of busy threads in the task worker thread pool via CLI (management API)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3333?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3333: ---------------------------------------- Fix Version/s: 4.0.0.Alpha1 Assignee: Masafumi Miura (was: David Lloyd) Resolution: Done > Expose number of busy threads in the task worker thread pool via CLI (management API) > ------------------------------------------------------------------------------------- > > Key: WFCORE-3333 > URL: https://issues.jboss.org/browse/WFCORE-3333 > Project: WildFly Core > Issue Type: Feature Request > Components: IO > Affects Versions: 3.0.4.Final > Reporter: Masafumi Miura > Assignee: Masafumi Miura > Fix For: 4.0.0.Alpha1 > > > WFLY-8203 / XNIO-283 exposed number of busy threads in the task worker thread pool via JMX. It would be useful to expose the metric via CLI (management API). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

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

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1750?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-1750: --------------------------------------- [~rudyatleti] ok. Red Hat offers patches and support for older releases of the product. If your customer has a Red Hat subscription, just ask him to move to the latest patch where this is fixed. > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3323) Initial Elytron configuration includes mapping-mode="first" in simple-permission-mapper

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3323?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3323: ---------------------------------------- Fix Version/s: 4.0.0.Alpha1 3.0.5.Final Assignee: ehsavoie Hugonnet (was: Ilia Vassilev) Resolution: Done > Initial Elytron configuration includes mapping-mode="first" in simple-permission-mapper > --------------------------------------------------------------------------------------- > > Key: WFCORE-3323 > URL: https://issues.jboss.org/browse/WFCORE-3323 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.3.Final > Reporter: Ondrej Lukas > Assignee: ehsavoie Hugonnet > Priority: Minor > Fix For: 4.0.0.Alpha1, 3.0.5.Final > > > As part of fix JBEAP-12933 there was added attribute {{mapping-mode="first"}} into "default-permission-mapper" {{simple-permission-mapper}} in default configuration. Value {{first}} is default value of {{simple-permission-mapper.mapping-mode}} which means that this attribute disappears after first change in server configuration. It can be confusing since Elytron subsystem configuration in XML is changed even if there was no request for changing that configuration. Attribute {{mapping-mode="first"}} should be removed from default configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

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 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, 1 month

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, 1 month

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, 1 month

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, 1 month

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, 1 month

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 October 2017