[JBoss JIRA] (ELY-718) Problems with creating CredentialStore from scratch when directory path doesn't exist.
by Hynek Švábek (JIRA)
Hynek Švábek created ELY-718:
--------------------------------
Summary: Problems with creating CredentialStore from scratch when directory path doesn't exist.
Key: ELY-718
URL: https://issues.jboss.org/browse/ELY-718
Project: WildFly Elytron
Issue Type: Bug
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
There are problems with creating CredentialStore from scratch when directory path doesn't exist.
*How to reproduce*
* /subsystem=elytron/credential-store=cs007:add(uri="cr-store://test/folderNotExist/keystorecs007.jceks?store.password=pass123;create.storage=true")
* /subsystem=elytron/credential-store=cs007/alias=newCs007:add(secret-value=Elytron)
*You can see this error message*
{code}
{
"outcome" => "failed",
"failure-description" => "WFLYELY00009: Unable to complete operation. 'ELY09504: Cannot write storage file '/home/hsvabek/securityworkspace/AAA_prezentace/jboss-eap-7.1.0.DR7/standalone/data/folderNotExist/keystorecs007.jceks' for the store 'cs007''",
"rolled-back" => true
}
{code}
When you execute repeatedly last command /subsystem=elytron/credential-store=cs007/alias=newCs007:add(secret-value=Elytron)
you get information about duplicate resource. It's mean the entry is in Credential Store (in memory) but not in file...
{code}
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0212: Duplicate resource [
(\"subsystem\" => \"elytron\"),
(\"credential-store\" => \"cs123\"),
(\"alias\" => \"newCs007\")
]",
"rolled-back" => true
}
{code}
*My suggestion solutions of this two problems:*
* try to create directory path
* when fails creating of CredentialStore file then we remove entry from memory too. It can be confusing have entry only in memory.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (ELY-718) Problems with creating CredentialStore from scratch when directory path doesn't exist.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-718?page=com.atlassian.jira.plugin.sy... ]
Hynek Švábek reassigned ELY-718:
--------------------------------
Assignee: Peter Skopek (was: Darran Lofthouse)
> Problems with creating CredentialStore from scratch when directory path doesn't exist.
> --------------------------------------------------------------------------------------
>
> Key: ELY-718
> URL: https://issues.jboss.org/browse/ELY-718
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Hynek Švábek
> Assignee: Peter Skopek
>
> There are problems with creating CredentialStore from scratch when directory path doesn't exist.
> *How to reproduce*
> * /subsystem=elytron/credential-store=cs007:add(uri="cr-store://test/folderNotExist/keystorecs007.jceks?store.password=pass123;create.storage=true")
> * /subsystem=elytron/credential-store=cs007/alias=newCs007:add(secret-value=Elytron)
> *You can see this error message*
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY00009: Unable to complete operation. 'ELY09504: Cannot write storage file '/home/hsvabek/securityworkspace/AAA_prezentace/jboss-eap-7.1.0.DR7/standalone/data/folderNotExist/keystorecs007.jceks' for the store 'cs007''",
> "rolled-back" => true
> }
> {code}
> When you execute repeatedly last command /subsystem=elytron/credential-store=cs007/alias=newCs007:add(secret-value=Elytron)
> you get information about duplicate resource. It's mean the entry is in Credential Store (in memory) but not in file...
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0212: Duplicate resource [
> (\"subsystem\" => \"elytron\"),
> (\"credential-store\" => \"cs123\"),
> (\"alias\" => \"newCs007\")
> ]",
> "rolled-back" => true
> }
> {code}
> *My suggestion solutions of this two problems:*
> * try to create directory path
> * when fails creating of CredentialStore file then we remove entry from memory too. It can be confusing have entry only in memory.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7462) Do not log common CLI failures for Elytron to server log
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-7462?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-7462:
----------------------------------------
FWIW, I was curious why this would be happening and looked at the elytron code related to the add op invoked in the reprocer steps to try and see. I saw nothing wrong. Then I tried to reproduce and couldn't. This was using current WildFly master so perhaps whatever the issue was has been corrected.
> Do not log common CLI failures for Elytron to server log
> --------------------------------------------------------
>
> Key: WFLY-7462
> URL: https://issues.jboss.org/browse/WFLY-7462
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
> Labels: user_experience
>
> Almost every common CLI command failure from Elytron subsystem is logged as ERROR to server log. For example this means:
> * trying to add duplicate resource -> ERROR in server log
> * missing required attribute of any resource attribute in CLI command -> ERROR in server log
> * missing capability -> ERROR in server log
> * ...
> Some reasons why these logs should not be logged to server log:
> * Adding useless messages to server log.
> * This is inconsistent with other subsystems (e.g. PicketBox). It can be confusing.
> These common CLI command failures should be removed from the log, or logged on low level (i.e. DEBUG)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7175) Complex type ssl-session in Elytron subsystem
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7175?page=com.atlassian.jira.plugin.... ]
Jan Kalina updated WFLY-7175:
-----------------------------
Summary: Complex type ssl-session in Elytron subsystem (was: Complex type server-ssl-context in Elytron subsystem)
> Complex type ssl-session in Elytron subsystem
> ---------------------------------------------
>
> Key: WFLY-7175
> URL: https://issues.jboss.org/browse/WFLY-7175
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Critical
>
> Elytron subsystem uses complex type in server-ssl-context resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details.
> Details: *server-ssl-context/ssl-session* - nested complex attributes (not critical in the short term - although exposing management information that provides insight into the current sessions would be a big bonus for administrators)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7175) Complex type server-ssl-context/ssl-session in Elytron subsystem
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7175?page=com.atlassian.jira.plugin.... ]
Jan Kalina updated WFLY-7175:
-----------------------------
Summary: Complex type server-ssl-context/ssl-session in Elytron subsystem (was: Complex type ssl-session in Elytron subsystem)
> Complex type server-ssl-context/ssl-session in Elytron subsystem
> ----------------------------------------------------------------
>
> Key: WFLY-7175
> URL: https://issues.jboss.org/browse/WFLY-7175
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Critical
>
> Elytron subsystem uses complex type in server-ssl-context resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details.
> Details: *server-ssl-context/ssl-session* - nested complex attributes (not critical in the short term - although exposing management information that provides insight into the current sessions would be a big bonus for administrators)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7175) Complex type server-ssl-context in Elytron subsystem
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-7175?page=com.atlassian.jira.plugin.... ]
Jan Kalina updated WFLY-7175:
-----------------------------
Description:
Elytron subsystem uses complex type in server-ssl-context resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details.
Details: *server-ssl-context/ssl-session* - nested complex attributes (not critical in the short term - although exposing management information that provides insight into the current sessions would be a big bonus for administrators)
was:Elytron subsystem uses complex type in server-ssl-context resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details.
> Complex type server-ssl-context in Elytron subsystem
> ----------------------------------------------------
>
> Key: WFLY-7175
> URL: https://issues.jboss.org/browse/WFLY-7175
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.Alpha1
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Critical
>
> Elytron subsystem uses complex type in server-ssl-context resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details.
> Details: *server-ssl-context/ssl-session* - nested complex attributes (not critical in the short term - although exposing management information that provides insight into the current sessions would be a big bonus for administrators)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1928) :validate-operation operation produces unclear failure message; pollutes server log with exceptions
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1928?page=com.atlassian.jira.plugi... ]
Kabir Khan reopened WFCORE-1928:
--------------------------------
> :validate-operation operation produces unclear failure message; pollutes server log with exceptions
> ---------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1928
> URL: https://issues.jboss.org/browse/WFCORE-1928
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 3.0.0.Alpha11
> Reporter: Michal Jurc
> Assignee: Kabir Khan
>
> Operation {{:validate-operation}} produces {{java.util.NoSuchElementException}} when no parameter is passed to it, polluting the server log with warning with stack trace.
> {{jboss-cli}}:
> {code}[standalone@localhost:9990 /] :validate-operation
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.util.NoSuchElementException: No child 'value' exists",
> "rolled-back" => true
> }
> {code}
> {code}08:58:13,409 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 17) WFLYCTL0013: Operation ("validate-operation") failed - address: ([]): java.util.NoSuchElementException: No child 'value' exists
> at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:387)
> at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:302)
> at org.jboss.dmr.ModelNode.require(ModelNode.java:875)
> at org.jboss.as.controller.operations.common.ValidateOperationHandler.execute(ValidateOperationHandler.java:91)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
> Upon passing this operation an illegal parameter, {{java.lang.IllegalArgumentException}} is produced instead of well formed failure message.
> {{jboss-cli}}:
> {code}[standalone@localhost:9990 /] :validate-operation(value=nonsense)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException",
> "rolled-back" => true
> }
> {code}
> {{server.log}}:
> {code}09:01:10,367 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 19) WFLYCTL0013: Operation ("validate-operation") failed - address: ([]): java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.getChild(ModelValue.java:115)
> at org.jboss.dmr.ModelNode.get(ModelNode.java:861)
> at org.jboss.as.controller.operations.common.ValidateOperationHandler.execute(ValidateOperationHandler.java:92)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
> This usage, however, does not pollute the server log with warning with stack trace:
> {{jboss-cli}}:
> {code}[standalone@localhost:9990 /] :validate-operation(value={"nonsense" => "nonsense"})
> Failed to handle ':validate-operation(value={"nonsense" => "nonsense"})': java.lang.IllegalArgumentException
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1928) :validate-operation operation produces unclear failure message; pollutes server log with exceptions
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1928?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-1928.
------------------------------
Resolution: Duplicate Issue
Duplicates WFCORE-1926
> :validate-operation operation produces unclear failure message; pollutes server log with exceptions
> ---------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1928
> URL: https://issues.jboss.org/browse/WFCORE-1928
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Affects Versions: 3.0.0.Alpha11
> Reporter: Michal Jurc
> Assignee: Kabir Khan
>
> Operation {{:validate-operation}} produces {{java.util.NoSuchElementException}} when no parameter is passed to it, polluting the server log with warning with stack trace.
> {{jboss-cli}}:
> {code}[standalone@localhost:9990 /] :validate-operation
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.util.NoSuchElementException: No child 'value' exists",
> "rolled-back" => true
> }
> {code}
> {code}08:58:13,409 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 17) WFLYCTL0013: Operation ("validate-operation") failed - address: ([]): java.util.NoSuchElementException: No child 'value' exists
> at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:387)
> at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:302)
> at org.jboss.dmr.ModelNode.require(ModelNode.java:875)
> at org.jboss.as.controller.operations.common.ValidateOperationHandler.execute(ValidateOperationHandler.java:91)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
> Upon passing this operation an illegal parameter, {{java.lang.IllegalArgumentException}} is produced instead of well formed failure message.
> {{jboss-cli}}:
> {code}[standalone@localhost:9990 /] :validate-operation(value=nonsense)
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException",
> "rolled-back" => true
> }
> {code}
> {{server.log}}:
> {code}09:01:10,367 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 19) WFLYCTL0013: Operation ("validate-operation") failed - address: ([]): java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.getChild(ModelValue.java:115)
> at org.jboss.dmr.ModelNode.get(ModelNode.java:861)
> at org.jboss.as.controller.operations.common.ValidateOperationHandler.execute(ValidateOperationHandler.java:92)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
> This usage, however, does not pollute the server log with warning with stack trace:
> {{jboss-cli}}:
> {code}[standalone@localhost:9990 /] :validate-operation(value={"nonsense" => "nonsense"})
> Failed to handle ':validate-operation(value={"nonsense" => "nonsense"})': java.lang.IllegalArgumentException
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months