September 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2180) Thread threads pools inherit security context of submitting threads

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2180?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-2180: -------------------------------------- Basically the way to fix this is to make sure that every thread pool we use uses a factory that sets the correct access control context for created threads. This can be easily done using a JBossThreadFactory. > Thread threads pools inherit security context of submitting threads > ------------------------------------------------------------------- > > Key: WFLY-2180 > URL: https://issues.jboss.org/browse/WFLY-2180 > Project: WildFly > Issue Type: Bug > Components: EE, EJB, Server, Web (Undertow) > Affects Versions: 8.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: David Lloyd > > Some thread pool implementation will immediately create a new thread if work is submitted and there is not enough threads available to handle it. This newly created thread will inherit the access control context of the thread that is submitting the work, which essentially means that thread pool threads have a random access control context. > This is the root cause of UNDERTOW-102, and likely other security manager related failures as well. > I think that the best way to fix this is in the thread pool itself, as it should create the thread in a privileged block. We obviously cannot do this for JDK thread pools however. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2181) TempFileProviderService creates a static, non-daemon thread pool

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2181?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2181: ----------------------------------------------- Stuart Douglas <sdouglas(a)redhat.com> made a comment on [bug 1012968|https://bugzilla.redhat.com/show_bug.cgi?id=1012968] https://github.com/jbossas/jboss-eap/pull/491 > TempFileProviderService creates a static, non-daemon thread pool > ---------------------------------------------------------------- > > Key: WFLY-2181 > URL: https://issues.jboss.org/browse/WFLY-2181 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > This can prevent the server from shutting down -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1709) Logging: convert the most important WARN and ERROR messages to use IDs and resource bundles

by Bela Ban (JIRA)

Bela Ban created JGRP-1709: ------------------------------ Summary: Logging: convert the most important WARN and ERROR messages to use IDs and resource bundles Key: JGRP-1709 URL: https://issues.jboss.org/browse/JGRP-1709 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.4 Convert WARN and ERROR messages that might be seen by users to use a resource bundle (conf/jg-messages*.properties) and assign unique IDs the those messages. Link in BZ: https://bugzilla.redhat.com/show_bug.cgi?id=999671 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1709) Logging: convert the most important WARN and ERROR messages to use IDs and resource bundles

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1709?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1709: -------------------------------- Since I want to release 3.4.0.Final by Oct 4, only the most prominent messages are going to be converted in 3.4. The rest of the work will be done in 3.5. > Logging: convert the most important WARN and ERROR messages to use IDs and resource bundles > ------------------------------------------------------------------------------------------- > > Key: JGRP-1709 > URL: https://issues.jboss.org/browse/JGRP-1709 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.4 > > > Convert WARN and ERROR messages that might be seen by users to use a resource bundle (conf/jg-messages*.properties) and assign unique IDs the those messages. > Link in BZ: https://bugzilla.redhat.com/show_bug.cgi?id=999671 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2181) TempFileProviderService creates a static, non-daemon thread pool

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2181?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2181: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1012968 > TempFileProviderService creates a static, non-daemon thread pool > ---------------------------------------------------------------- > > Key: WFLY-2181 > URL: https://issues.jboss.org/browse/WFLY-2181 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > This can prevent the server from shutting down -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2181) TempFileProviderService creates a static, non-daemon thread pool

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-2181: ------------------------------------ Summary: TempFileProviderService creates a static, non-daemon thread pool Key: WFLY-2181 URL: https://issues.jboss.org/browse/WFLY-2181 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 8.0.0.Alpha4 Reporter: Stuart Douglas Assignee: Stuart Douglas This can prevent the server from shutting down -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-276) Stream mode with CR4-Pre1 generates rules looping

by Richard Bourner (JIRA)

[ https://issues.jboss.org/browse/DROOLS-276?page=com.atlassian.jira.plugin... ] Richard Bourner updated DROOLS-276: ----------------------------------- Priority: Blocker (was: Major) > Stream mode with CR4-Pre1 generates rules looping > -------------------------------------------------- > > Key: DROOLS-276 > URL: https://issues.jboss.org/browse/DROOLS-276 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR4 > Environment: Drools 6.0.0.CR4-Pre1 > Reporter: Richard Bourner > Assignee: Mark Proctor > Priority: Blocker > Attachments: Drools6Stream.zip > > > When in STREAM mode, our rules are looping because of an update. > The attached example doesn't demonstrate the looping but one rule is fired twice where it should only fire once. We are supposing that the issue is the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2139) ProxyStepHandler/Controller need to check access before attempting to read information

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2139?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2139: ----------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> changed the Status of [bug 1010672|https://bugzilla.redhat.com/show_bug.cgi?id=1010672] from ON_QA to VERIFIED > ProxyStepHandler/Controller need to check access before attempting to read information > -------------------------------------------------------------------------------------- > > Key: WFLY-2139 > URL: https://issues.jboss.org/browse/WFLY-2139 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Beta1 > > > This affects things like recursive :read-resource(-description) :read-children-resources and so on. The problem as it stands is that if you have, say, a host scoped role scoped to host=master, and there is also a slave host controller, and you try to :read-resource(recursive=true,proxies=true), the master will list the slave host controller in its list of child addresses. It will then execute /host=slave:read-resource(recursive=true,proxies=true), which will fail and roll back the tx since the master host scoped role does not have access to that resource. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2139) ProxyStepHandler/Controller need to check access before attempting to read information

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2139?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2139: ----------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> made a comment on [bug 1010672|https://bugzilla.redhat.com/show_bug.cgi?id=1010672] Verified 6.2.0.ER3 > ProxyStepHandler/Controller need to check access before attempting to read information > -------------------------------------------------------------------------------------- > > Key: WFLY-2139 > URL: https://issues.jboss.org/browse/WFLY-2139 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Beta1 > > > This affects things like recursive :read-resource(-description) :read-children-resources and so on. The problem as it stands is that if you have, say, a host scoped role scoped to host=master, and there is also a slave host controller, and you try to :read-resource(recursive=true,proxies=true), the master will list the slave host controller in its list of child addresses. It will then execute /host=slave:read-resource(recursive=true,proxies=true), which will fail and roll back the tx since the master host scoped role does not have access to that resource. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2089) Error executing composite operation as server group role

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2089?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2089: ----------------------------------------------- Jakub Cechacek <jcechace(a)redhat.com> made a comment on [bug 1008087|https://bugzilla.redhat.com/show_bug.cgi?id=1008087] verified 6.2.0.ER3 > Error executing composite operation as server group role > -------------------------------------------------------- > > Key: WFLY-2089 > URL: https://issues.jboss.org/browse/WFLY-2089 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Affects Versions: 8.0.0.Alpha4 > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 8.0.0.Beta1 > > > This role > {noformat} > [domain@localhost:9999 /] /core-service=management/access=authorization/server-group-scoped-role=main-MAINTAINER:read-resource > { > "outcome" => "success", > "result" => { > "base-role" => "MAINTAINER", > "server-groups" => ["main-server-group"] > } > } > {noformat} > ... executing this operation > {noformat} > [INFO] { > [INFO] "address" => [], > [INFO] "operation" => "composite", > [INFO] "steps" => [ > [INFO] { > [INFO] "address" => [], > [INFO] "operation" => "read-children-resources", > [INFO] "child-type" => "deployment" > [INFO] }, > [INFO] { > [INFO] "operation" => "read-children-resources", > [INFO] "child-type" => "server-group" > [INFO] }, > [INFO] { > [INFO] "address" => [ > [INFO] ("server-group" => "*"), > [INFO] ("deployment" => "*") > [INFO] ], > [INFO] "operation" => "read-resource" > [INFO] } > [INFO] ] > [INFO] } > {noformat} > ... leads to: > {noformat} > [Host Controller] 19:37:41,713 FINE [com.sun.net.httpserver] (HttpManagementService-threads - 2) POST /management HTTP/1.1 [401 Unauthorized] () > [Host Controller] 19:37:41,713 FINE [com.sun.net.httpserver] (HttpManagementService-threads - 1) POST /management HTTP/1.1 [401 Unauthorized] () > [Host Controller] 19:37:41,762 FINE [com.sun.net.httpserver] (HttpManagementService-threads - 2) POST /management HTTP/1.1 [200 OK] () > [Host Controller] 19:37:41,766 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 1) JBAS014616: Operation ("resolve") failed - address: ([]) - failure description: "JBAS013456: Unauthorized to execute operation 'resolve' for resource '[]' -- \"JBAS013475: Permission denied\"" > [Host Controller] 19:37:41,767 FINE [com.sun.net.httpserver] (HttpManagementService-threads - 1) POST /management HTTP/1.1 [500 Internal Server Error] () > [Host Controller] 19:37:41,821 FINE [com.sun.net.httpserver] (HttpManagementService-threads - 1) POST /management HTTP/1.1 [200 OK] () > [Host Controller] 19:37:41,852 DEBUG [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 2) JBAS014616: Operation ("composite") failed - address: ([]) - failure description: "JBAS014883: No resource definition is registered for address [ > [Host Controller] (\"host\" => \"master\"), > [Host Controller] (\"server\" => \"server-two\") > [Host Controller] ]" > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 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 2013