[JBoss JIRA] (WFCORE-2283) Make 'required' attributes clearer when using tab completion within CLI
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2283?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-2283:
------------------------------------------
Some random thoughts...
One is if I'm looking for something and it isn't proposed, I'm going to be confused and, if it happens a lot, eventually mad. So how to mitigate that?
* If they hit tab twice, show them all?
* If the list is short, show them all? I think this is particularly relevant if the user has typed something before hitting tab.
* Some kind of text output before the list that indicates the list is filtered?
Another thing is there are other useful relationships besides whether an attribute is required. For example
A -- required, alternate is B
B -- required, alternate is A
C -- required
D -- not required, requires A
If I added A to the operation, and then hit tab, I'd want to see D even though it's not required. I configured A which means I've expressed interest in the "A functionality" and therefore the related D should be shown. (I also wouldn't want to see B since it is illegal now.)
The downside to all this stuff I mention here is there's no longer any obvious to the user rule to explain when stuff appears. So it could seem a bit mysterious. Having an easy way to get an unfiltered list (e.g. second tab) would help mitigate that.
An easy way to get the unfiltered list is also a built-in workaround to the bugs that are likely to crop up with this.
> Make 'required' attributes clearer when using tab completion within CLI
> -----------------------------------------------------------------------
>
> Key: WFCORE-2283
> URL: https://issues.jboss.org/browse/WFCORE-2283
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Reporter: Darran Lofthouse
> Assignee: Jean-Francois Denise
>
> The following is some example output pressing tab to reveal the parameters of 'add': -
> {{[standalone@localhost:9990 /] ./subsystem=elytron/key-store=localhost:add(
> ! alias-filter credential-reference path provider-name providers relative-to required type }}
> From this is it not clear which are actually required.
> Suggestions to make it clearer: -
> * Show required / optional in different colours.
> * Add something to the required attributes e.g. '*'
> * Add something to the optional requirements e.g. {optional_arg}
> Maybe this can go one step further and take into account arguments already added by the user, especially where attributes require another attribute or are an alternative.
> Once an attribute is identified as being an alternative to another attribute maybe it should be omitted altogether from the list or maybe also have something adding to it !attr_name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2532) Some logging tests fail with security manager in WF core
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2532?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-2532:
---------------------------------------
We likely just need to wrap the {{TestSuiteEnvironment.getSystemProperty()}} with privileged block. Any test using that will have issues. In the logging cases it's {{TestSuiteEnvironment.getHttpAddress()}} that's causing the issue.
> Some logging tests fail with security manager in WF core
> --------------------------------------------------------
>
> Key: WFCORE-2532
> URL: https://issues.jboss.org/browse/WFCORE-2532
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging, Test Suite
> Reporter: Jan Tymel
> Assignee: James Perkins
>
> * *org.jboss.as.test.integration.logging.operations.CustomFormattersTestCase*
> * *org.jboss.as.test.integration.logging.operations.CustomHandlerOperationsTestCase*
> * *org.jboss.as.test.integration.logging.operations.CustomHandlerTestCase*
> * *org.jboss.as.test.integration.logging.operations.Log4jCustomHandlerTestCase*
> * *org.jboss.as.test.integration.logging.perdeploy.JBossLog4jXmlTestCase*
> * *org.jboss.as.test.integration.logging.perdeploy.JBossLoggingPropertiesTestCase*
> * *org.jboss.as.test.integration.logging.perdeploy.Log4jPropertiesTestCase*
> * *org.jboss.as.test.integration.logging.perdeploy.Log4jXmlTestCase*
> * *org.jboss.as.test.integration.logging.perdeploy.LoggingPropertiesTestCase*
> * *org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase*
> * *org.jboss.as.test.integration.logging.profiles.NonExistingProfileTestCase*
> * *org.jboss.as.test.integration.logging.syslog.SyslogHandlerTestCase*
> {{cd testsuite/standalone/}}
> {{mvn test -Dtest=org.jboss.as.test.integration.logging.**.* -Dsecurity.manager}}
> {code}
> org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: java.lang.Exception: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"logging1.jar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"logging1.jar\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"logging1.jar\"
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission \"(\"java.util.PropertyPermission\" \"jboss.bind.address\" \"read\")\" in code source \"(vfs:/content/logging1.jar <no signer certificates>)\" of \"ModuleClassLoader for Module \"deployment.logging1.jar\" from Service Module Loader\")"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"logging1.jar\".INSTALL"]
> }
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
> at org.jboss.as.test.integration.logging.AbstractLoggingTestCase.deploy(AbstractLoggingTestCase.java:168)
> at org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase.deploy(LoggingProfilesTestCase.java:314)
> at org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase.deploy(LoggingProfilesTestCase.java:304)
> at org.jboss.as.test.integration.logging.profiles.LoggingProfilesTestCase.testProfiles(LoggingProfilesTestCase.java:201
> {code}
> * *org.jboss.as.test.manualmode.logging.Log4jAppenderTestCase*
> * *org.jboss.as.test.manualmode.logging.LoggingPreferencesTestCase*
> * *org.jboss.as.test.manualmode.logging.PerDeployLoggingTestCase*
> * *org.jboss.as.test.manualmode.logging.ReconnectSyslogServerTestCase*
> * *org.jboss.as.test.manualmode.logging.SizeAppenderRestartTestCase*
> * *org.jboss.as.test.manualmode.logging.SyslogIsNotAvailableDuringServerBootTestCase*
> {{cd testsuite/manualmode/}}
> {{mvn test -Dtest=org.jboss.as.test.manualmode.logging.* -Dsecurity.manager}}
> {code}
> org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper$ServerDeploymentException: java.lang.Exception: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"logging-test.jar\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"logging-test.jar\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"logging-test.jar\"
> Caused by: java.security.AccessControlException: WFSM000001: Permission check failed (permission \"(\"java.util.PropertyPermission\" \"jboss.bind.address\" \"read\")\" in code source \"(vfs:/content/logging-test.jar <no signer certificates>)\" of \"ModuleClassLoader for Module \"deployment.logging-test.jar\" from Service Module Loader\")"},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"logging-test.jar\".INSTALL"]
> }
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85)
> at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42)
> at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55)
> at org.wildfly.core.testrunner.ServerController.deploy(ServerController.java:92)
> at org.jboss.as.test.manualmode.logging.AbstractLoggingTestCase.deploy(AbstractLoggingTestCase.java:197)
> at org.jboss.as.test.manualmode.logging.Log4jAppenderTestCase.startContainer(Log4jAppenderTestCase.java:93)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2283) Make 'required' attributes clearer when using tab completion within CLI
by Jean-Francois Denise (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2283?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise commented on WFCORE-2283:
----------------------------------------------
Hi [~weeks.c],
we are proposing here a way to help Wildly Command Line (CLI) users to identify the required arguments when completing a management operation.
1) One way would be to "tag" exposed arguments to explicit their nature (required vs optional) (eg: asterisk for mandatory, brackets for optional, colouring or any other syntax element).
2) Another way would be to filter arguments. First expose required arguments then, once the operation contains all the mandatory ones, expose optional ones.
The second way has today my preference (not a lot of practice of it, just raw prototyping for now):
- No syntax marker to decode ("what this '*' means" kind of question)
- No confusion between what the completion exposes and what you get when selecting one of these items (tag being removed in the selected argument).
- No need for colouring (that color blinds would not take benefit of). Color seems to me not a good idea (specially in a command line/terminal context).
- More drive, the user is driven by the completer to choose arguments.
- Reduced amount of content exposed to the user.
- Allow for optimised cases. This is the case of a single required argument that would be automatically inlined when completing for the first time, the completer would then propose the list of optional arguments (if any).
- This is in line with some other part of the CLI where similar filtering is applied to expose command options (as opposed to operation arguments discussed there).
With this approach we are loosing the flat list (that contains all arguments) that can be seen as helpful to discover the whole set of arguments in a single <TAB> action when you have both required and optional arguments. In this case you will discover them all but in 2 steps.
Users could think that there are ONLY required attributes although the right way to properly discover the set or operation arguments is by using the help command. help describes the operation synopsis that contains details on required/optional arguments (description and typing).
help extract:
help /subsystem=logging/logger=sun.rmi:list-add
SYNOPSIS
list-add(name=<a string>, [index=<an integer>], [value=<a string>])
If you are interested by discussing this topic, we could exchange more on it.
Thanks.
JF
> Make 'required' attributes clearer when using tab completion within CLI
> -----------------------------------------------------------------------
>
> Key: WFCORE-2283
> URL: https://issues.jboss.org/browse/WFCORE-2283
> Project: WildFly Core
> Issue Type: Feature Request
> Components: CLI
> Reporter: Darran Lofthouse
> Assignee: Jean-Francois Denise
>
> The following is some example output pressing tab to reveal the parameters of 'add': -
> {{[standalone@localhost:9990 /] ./subsystem=elytron/key-store=localhost:add(
> ! alias-filter credential-reference path provider-name providers relative-to required type }}
> From this is it not clear which are actually required.
> Suggestions to make it clearer: -
> * Show required / optional in different colours.
> * Add something to the required attributes e.g. '*'
> * Add something to the optional requirements e.g. {optional_arg}
> Maybe this can go one step further and take into account arguments already added by the user, especially where attributes require another attribute or are an alternative.
> Once an attribute is identified as being an alternative to another attribute maybe it should be omitted altogether from the list or maybe also have something adding to it !attr_name.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8376) ResourceAdapterPoolAttributesTestCase fails with security manager
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/WFLY-8376?page=com.atlassian.jira.plugin.... ]
Martin Simka updated WFLY-8376:
-------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/9846
> ResourceAdapterPoolAttributesTestCase fails with security manager
> -----------------------------------------------------------------
>
> Key: WFLY-8376
> URL: https://issues.jboss.org/browse/WFLY-8376
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Jan Tymel
> Assignee: Martin Simka
>
> *org.jboss.as.test.integration.jca.poolattributes.ResourceAdapterPoolAttributesTestCase#testModifyPoolAttributes*
> {{./integration-tests.sh -DtestLogToFile=false -Dts.noSmoke -Dts.basic -Dtest=ResourceAdapterPoolAttributesTestCase -Dsecurity.manager}}
> {code}
> SEVERE [org.jboss.arquillian.protocol.jmx.JMXTestRunner] (pool-3-thread-1) Failed: org.jboss.as.test.integration.jca.poolattributes.ResourceAdapterPoolAttributesTestCase.testModifyPoolAttributes: java.lang.AssertionError: WFSM000001: Permission check failed (permission "("java.lang.reflect.ReflectPermission" "suppressAccessChecks")" in code source "(vfs:/content/pool-attributes-test.rar/pool-attributes-test.jar <no signer certificates>)" of "ModuleClassLoader for Module "deployment.pool-attributes-test.rar" from Service Module Loader")
> at org.junit.Assert.fail(Assert.java:88)
> at org.jboss.as.test.integration.jca.JcaTestsUtil.extractConnectionManager(JcaTestsUtil.java:144)
> at org.jboss.as.test.integration.jca.JcaTestsUtil.exctractPoolConfiguration(JcaTestsUtil.java:89)
> at org.jboss.as.test.integration.jca.poolattributes.ResourceAdapterPoolAttributesTestCase.testModifyPoolAttributes(ResourceAdapterPoolAttributesTestCase.java:137)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:374)
> at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.container.test.impl.execution.ContainerTestExecuter.execute(ContainerTestExecuter.java:38)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:136)
> at org.jboss.arquillian.junit.Arquillian$8.evaluate(Arquillian.java:367)
> at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:245)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:426)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
> at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:259)
> at org.jboss.arquillian.junit.Arquillian$7$1.invoke(Arquillian.java:319)
> at org.jboss.arquillian.container.test.impl.execution.BeforeLifecycleEventExecuter.on(BeforeLifecycleEventExecuter.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:130)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.fireCustomLifecycle(EventTestRunnerAdaptor.java:159)
> at org.jboss.arquillian.junit.Arquillian$7.evaluate(Arquillian.java:312)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:204)
> at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:426)
> at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:54)
> at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:218)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:166)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at org.jboss.arquillian.junit.container.JUnitTestRunner.execute(JUnitTestRunner.java:66)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.doRunTestMethod(JMXTestRunner.java:180)
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.doRunTestMethod(ArquillianService.java:200)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:162)
> at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:141)
> at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:176)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:83)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:287)
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:124)
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:58)
> at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:249)
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:150)
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:264)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:831)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:813)
> at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.invoke(PluggableMBeanServerImpl.java:1512)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:731)
> at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168)
> at org.jboss.as.jmx.AuthorizingMBeanServer.invoke(AuthorizingMBeanServer.java:258)
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:277)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.lang.Thread.run(Thread.java:785)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month