[
https://issues.jboss.org/browse/WFLY-7462?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-7462:
----------------------------------------
The issues driving this (see discussion in JBEAP-6859) are now fixed in WildFly Core, so
this can be resolved once core 3.0.0.Beta5 is integrated into full sometime in the next
week. I plan to resolve this but am just commenting here in case I forget.
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
Fix For: 11.0.0.Alpha1
Almost every common CLI command failure from Elytron subsystem is logged as ERROR to
server log. For example this means:
* trying to add duplicate service -> 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)