Details
-
Bug
-
Resolution: Done
-
Critical
-
7.1.0.DR7
-
Not Required
-
Description
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)
Attachments
Issue Links
- is blocked by
-
JBEAP-8840 Use RuntimeCapability.Builder.setAllowMultipleRegistrations(...) where appropriate
- Verified
-
JBEAP-9004 broadcast-group capability must include the messaging server name
- Verified
-
WFCORE-2249 ObjectTypeValidator only validates fields the user provides
- Resolved
-
WFCORE-2270 Capability registry should not allow more than one registration point for a RuntimeCapabilityRegistration
- Resolved
-
JBEAP-8693 Subsystem tests are registering the same capability in multiple spots; clean this up
- Verified
- is cloned by
-
WFLY-7462 Do not log common CLI failures for Elytron to server log
- Closed
- is incorporated by
-
JBEAP-8874 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta6
- Verified