Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-6859

Do not log common CLI failures for Elytron to server log

    XMLWordPrintable

Details

    • Not Required
    • Hide

      There are many ways how to reproduce it, e.g.:

      /subsystem=elytron/properties-realm=realm:add(users-properties={})
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0155: path may not be null",
    "rolled-back" => true
}

      You will see in server log:

      ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 56) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "elytron"),
    ("properties-realm" => "realm")
]) - failure description: "WFLYCTL0155: path may not be null"
      Show
      There are many ways how to reproduce it, e.g.: /subsystem=elytron/properties-realm=realm:add(users-properties={}) { "outcome" => "failed" , "failure-description" => "WFLYCTL0155: path may not be null " , "rolled-back" => true } You will see in server log: ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 56) WFLYCTL0013: Operation ( "add" ) failed - address: ([ ( "subsystem" => "elytron" ), ( "properties-realm" => "realm" ) ]) - failure description: "WFLYCTL0155: path may not be null "

    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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8840 Use RuntimeCapability.Builder.setAllowMultipleRegistrations(...) where appropriate

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9004 broadcast-group capability must include the messaging server name

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2249 ObjectTypeValidator only validates fields the user provides

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2270 Capability registry should not allow more than one registration point for a RuntimeCapabilityRegistration

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. JBEAP-8693 Subsystem tests are registering the same capability in multiple spots; clean this up

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7462 Do not log common CLI failures for Elytron to server log

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-8874 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta6

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              bstansbe@redhat.com Brian Stansberry
              olukas Ondrej Lukas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: