Loading...

XML

Word

Printable

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Release Note Status:
Not Required
Target Release:

7.1.0.GA
Steps to Reproduce:
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 "

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)

is blocked by

WFCORE-2249 ObjectTypeValidator only validates fields the user provides

WFCORE-2270 Capability registry should not allow more than one registration point for a RuntimeCapabilityRegistration

JBEAP-8840 Use RuntimeCapability.Builder.setAllowMultipleRegistrations(...) where appropriate

JBEAP-9004 broadcast-group capability must include the messaging server name

JBEAP-8693 Subsystem tests are registering the same capability in multiple spots; clean this up

is cloned by

WFLY-7462 Do not log common CLI failures for Elytron to server log

is incorporated by

JBEAP-8874 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta6

(1 is cloned by, 1 is incorporated by)