[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 commented on WFLY-2183:
-----------------------------------
It's a server side issue. The attributes are flagged as "writable=false":
{noformat}
[domain@localhost:9999 /] /profile=default/subsystem=logging/custom-handler=*:read-resource-description(access-control=trim-descriptions, operations=true){role=administrator}
{
"outcome" => "success",
"result" => [{
"address" => [
("profile" => "default"),
("subsystem" => "logging"),
("custom-handler" => "*")
],
"outcome" => "success",
"result" => {
"description" => undefined,
"attributes" => undefined,
"operations" => undefined,
"children" => {},
"access-control" => {
"default" => {
"read" => true,
"write" => true,
"attributes" => {
"enabled" => {
"read" => true,
"write" => true
},
"module" => {
"read" => true,
"write" => false
},
"class" => {
"read" => true,
"write" => false
},
"properties" => {
"read" => true,
"write" => true
},
"formatter" => {
"read" => true,
"write" => true
},
"filter-spec" => {
"read" => true,
"write" => true
},
"level" => {
"read" => true,
"write" => true
},
"name" => {
"read" => true,
"write" => false
},
"encoding" => {
"read" => true,
"write" => true
},
"filter" => {
"read" => true,
"write" => true
}
},
"operations" => {
"read-children-names" => {"execute" => true},
"read-operation-description" => {"execute" => true},
"remove" => {"execute" => true},
"update-properties" => {"execute" => true},
"read-resource-description" => {"execute" => true},
"enable" => {"execute" => true},
"read-resource" => {"execute" => true},
"change-log-level" => {"execute" => true},
"add" => {"execute" => true},
"read-attribute" => {"execute" => true},
"whoami" => {"execute" => true},
"read-children-types" => {"execute" => true},
"read-operation-names" => {"execute" => true},
"undefine-attribute" => {"execute" => true},
"read-children-resources" => {"execute" => true},
"disable" => {"execute" => true},
"write-attribute" => {"execute" => true}
}
},
"exceptions" => {}
}
}
}]
}
{noformat}
> 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
10 years, 7 months
[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
10 years, 7 months
[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
10 years, 7 months