2 Replies Latest reply on Nov 7, 2011 9:16 AM by aloubyansky

    JBoss7 CLI logging setup

    r1em

      I would like to setup JBoss7 log setup with the CLI interface (jboss-admin).

      Unfortunatly it fails with an error:

       

      I use this command:

      /profile=default/subsystem=logging/periodic-rotating-file-handler=COA:add(append=false,autoflush=true,encoding="UTF-8",file={path="coa.log", relative-to="/tmp"},formatter="HHmmss",level="INFO",suffix="yyyyMMdd")

      {

          "outcome" => "failed",

          "result" => {"server-groups" => [("main-server-group" => {"master" => {

          "host" => "master",

          "response" => {

              "outcome" => "failed",

              "failure-description" => "Operation handler failed: java.lang.IllegalArgumentException: newValue is null",

              "rolled-back" => true

          }

      }})]},

          "failure-description" => "Operation failed or was rolled back on all servers.",

          "rolled-back" => true

      }

       

      Is this a bug, or am I doing something wrong?

       

       

        • 1. Re: JBoss7 CLI logging setup
          chrishiner

          Trying using => instead of = in the file={...} section:

          /profile=default/subsystem=logging/periodic-rotating-file-handler=COA:add(append=false,autoflush=true,encoding="UTF-8",file={path=>"coa.log", relative-to=>"/tmp"},formatter="HHmmss",level="INFO",suffix="yyyyMMdd")

           

          I'm not sure why the syntax varies inside {}, but it does.

          • 2. Re: JBoss7 CLI logging setup
            aloubyansky

            Chris is right. Complex values are accepted in the DMR format which is very unfriendly for typing.

            There already is an issue for this https://issues.jboss.org/browse/AS7-2088

            It's kind of not a bug, since it was consciously implemented that way and it's the native format of DMR but I also can't say that it's right.