1 Reply Latest reply on Apr 28, 2015 4:25 AM by dsteel100

    Issues creating root-logger in a logging-profile using CLI

    dsteel100 Newbie

      Hi, I am having issues creating a logging profile that contains root logging.  The commands that i am using are:

       

      /subsystem=logging/logging-profile=AXIS2:add

      /subsystem=logging/logging-profile=AXIS2/periodic-rotating-file-handler=SOAP:add(file={"path"=>"c:\\axis2.log"}, suffix=".yyyy.MM.dd")

      /subsystem=logging/logging-profile=AXIS2/periodic-rotating-file-handler=SOAP:write-attribute(name="formatter", value="%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n")

      /subsystem=logging/logging-profile=AXIS2/periodic-rotating-file-handler=SOAP:change-log-level(level="DEBUG")

       

      Which is fine and I can even add a context using:

       

      /subsystem=logging/logging-profile=AXIS2/logger=com.myApp:add(level=TRACE)

      /subsystem=logging/logging-profile=AXIS2/logger=com.myApp:assign-handler(name="SOAP")

       

      However when I try and create a root logger using:

       

      /subsystem=logging/logging-profile=AXIS2/root-logger=ROOT:root-logger-assign-handler(name="SOAP")

       

      But I get the following:

       

      {

          "outcome" => "failed",

          "failure-description" => "JBAS014807: Management resource '[

          (\"subsystem\" => \"logging\"),

          (\"logging-profile\" => \"AXIS2\"),

          (\"root-logger\" => \"ROOT\")

      ]' not found",

          "rolled-back" => true

      }

       

      If I add the section manually in the standalone.xml file it works, and i can use the command

       

      /subsystem=logging/logging-profile=AXIS2/root-logger=ROOT:read-resource

      It does see the resource.

       

      What is wrong with: /subsystem=logging/logging-profile=AXIS2/root-logger=ROOT:root-logger-assign-handler(name="SOAP")

       

      Regards,

       

      Dave