September 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-72) Release Remoting JMX 1.1.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-72?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-72: ----------------------------------------------- Ladislav Thon <lthon(a)redhat.com> made a comment on [bug 1007001|https://bugzilla.redhat.com/show_bug.cgi?id=1007001] Given that bug 1009762 is already verified, I think we can move this to the "verified" state too, even though the non-productized remoting-jmx 1.1.1 version has never made it to any EAP 6.2.0.ERx. > Release Remoting JMX 1.1.1.Final > -------------------------------- > > Key: REMJMX-72 > URL: https://issues.jboss.org/browse/REMJMX-72 > Project: Remoting JMX > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.1.Final > > > Release 1.1.1.Final -- 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

10 years, 6 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: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> made a comment on [bug 1012968|https://bugzilla.redhat.com/show_bug.cgi?id=1012968] I was able to hit this also on linux during scripts testing (FYI). > 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-72) Release Remoting JMX 1.1.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-72?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-72: ----------------------------------------------- Ladislav Thon <lthon(a)redhat.com> changed the Status of [bug 1007001|https://bugzilla.redhat.com/show_bug.cgi?id=1007001] from ON_QA to VERIFIED > Release Remoting JMX 1.1.1.Final > -------------------------------- > > Key: REMJMX-72 > URL: https://issues.jboss.org/browse/REMJMX-72 > Project: Remoting JMX > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.1.Final > > > Release 1.1.1.Final -- 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

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2131) read-operation-names to return a filtered list of allowed operations

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2131?page=com.atlassian.jira.plugin.... ] Kabir Khan commented on WFLY-2131: ---------------------------------- After speaking to Brian we decided to leave the plain :read-operation-names as it is for backwards compatibility, in case others than just CLI also rely on this operation. So to get the new behaviour I'll do 1) e.g. :read-operation-names(access-control=true). If 1) is done, you also get 2). 2) will be some header containing the stripped out operations, I will look at read-resource for inspiration. > read-operation-names to return a filtered list of allowed operations > -------------------------------------------------------------------- > > Key: WFLY-2131 > URL: https://issues.jboss.org/browse/WFLY-2131 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Alexey Loubyansky > Assignee: Kabir Khan > Fix For: 8.0.0.CR1 > > > As discussed on IRC with Kabir, Heiko and me, we agreed that read-operation-names should return only the operations the caller is permitted to execute. -- 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

10 years, 6 months

1
0
0 / 0

[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

10 years, 6 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

10 years, 6 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

10 years, 6 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

10 years, 6 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

10 years, 6 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

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2013