September 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2183: ----------------------------------------------- Heiko Braun <hbraun(a)redhat.com> changed the Status of [bug 1013521|https://bugzilla.redhat.com/show_bug.cgi?id=1013521] from ASSIGNED to NEW > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > -- 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-2183) Module and ClassName fields are disabled in new Custom handler dialog

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] Heiko Braun moved HAL-229 to WFLY-2183: --------------------------------------- Project: WildFly (was: HAL) Key: WFLY-2183 (was: HAL-229) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Domain Management (was: Core ) Security: (was: Public) Fix Version/s: 8.0.0.CR1 (was: Core 2.1.0.Final) > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 8.0.0.CR1 > > -- 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-2182) Significant slow down of testsuite execution

by Jozef Hartinger (JIRA)

Jozef Hartinger created WFLY-2182: ------------------------------------- Summary: Significant slow down of testsuite execution Key: WFLY-2182 URL: https://issues.jboss.org/browse/WFLY-2182 Project: WildFly Issue Type: Bug Components: Remoting Reporter: Jozef Hartinger Assignee: Kabir Khan I am observing a significant slow down when running the Weld integration testsuite. I tracked this down to this commit: https://github.com/wildfly/wildfly/commit/13f09525717a089f8a524d086fd8657... Here are the observed execution times of the Weld integration testsuite: Before: Total time: 4:30.357s After: Total time: 11:05.547s I also tried running the WildFly's integration testsuite (testsuite/integration/basic) with and without the 13f09525717a089f8a524d086fd865798410f368 commit: Before: Total time: 13:04.412s After: Total time: 21:33.089s Note that the difference is not observed when using the arquillian servlet protocol -- 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] (REMJMX-68) ClientConnection should propagate JMRuntimeException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-68?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-68: ----------------------------------------------- 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. > ClientConnection should propagate JMRuntimeException > ---------------------------------------------------- > > Key: REMJMX-68 > URL: https://issues.jboss.org/browse/REMJMX-68 > Project: Remoting JMX > Issue Type: Feature Request > Affects Versions: 2.0.0.CR1 > Reporter: Kabir Khan > Assignee: Darran Lofthouse > Fix For: 1.1.1.Final, 2.0.0.CR2 > > > It currently wraps these in an IOException. JMX Rbac uses RuntimeMBeanException for authorization failures. -- 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-895) JBoss crashes when run with AspectJ java agent

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-895?page=com.atlassian.jira.plugin.s... ] Stuart Douglas commented on WFLY-895: ------------------------------------- There is one thing we could have done to fix this, and that is to put the logmanager jar on the system class path, and make the logmanager module just have exported dependencies on the system paths. Obviously this is not ideal, but there have been quite a few cases where 3rd party javaagents have had this problem, and it would be better if they just worked. > JBoss crashes when run with AspectJ java agent > ---------------------------------------------- > > Key: WFLY-895 > URL: https://issues.jboss.org/browse/WFLY-895 > Project: WildFly > Issue Type: Bug > Components: Server > Environment: OS X 10.7.2, Ubuntu 11.10 > Reporter: Jack Lund > Assignee: David Lloyd > Labels: aspectj, load_time_weaving > > When trying to start JBoss with the AspectJ java agent (-javaagent:/path/aspectjweaver.jar) to enable load-time weaving, JBoss crashes with the following stack trace in the logs: > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/jack/jboss-as-7.1.0.CR1b > JAVA: java > JAVA_OPTS: -server -javaagent:/home/jack/aspectjweaver.jar -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true > ========================================================================= > WARNING: Failed to load the specified logmodule org.jboss.logmanager:main > Exception in thread "main" java.lang.ExceptionInInitializerError > at org.jboss.as.server.Main.main(Main.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.jboss.modules.Module.run(Module.java:248) > at org.jboss.modules.Main.main(Main.java:313) > Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") > at org.jboss.logmanager.Logger.getLogger(Logger.java:60) > at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42) > ... 7 more -- 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] (REMJMX-68) ClientConnection should propagate JMRuntimeException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-68?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-68: ----------------------------------------------- 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 > ClientConnection should propagate JMRuntimeException > ---------------------------------------------------- > > Key: REMJMX-68 > URL: https://issues.jboss.org/browse/REMJMX-68 > Project: Remoting JMX > Issue Type: Feature Request > Affects Versions: 2.0.0.CR1 > Reporter: Kabir Khan > Assignee: Darran Lofthouse > Fix For: 1.1.1.Final, 2.0.0.CR2 > > > It currently wraps these in an IOException. JMX Rbac uses RuntimeMBeanException for authorization failures. -- 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] (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

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: ----------------------------------------------- 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

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

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

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