2 Replies Latest reply on Sep 23, 2013 5:29 AM by ehugonnet

    configure logging filter with filter-spec from jboss-cli causes failure

    Chao Wang Newbie

      I'm trying to cofigure AS8 (jboss-as-8.0.0.Alpha1-SNAPSHOT) logging filter with "filter-spec", unfortunately I had a failed outcome with following message:

       

      [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter-spec,value="substituteAll("JBAS","EAP")")   

      {

          "outcome" => "failed",

          "failure-description" => "JBAS014749: Operation handler failed: Expected string next in filter expression",

          "rolled-back" => true

      }

       

      ModelNode from debug :

      {

          "level" => "INFO",

          "enabled" => undefined,

          "encoding" => undefined,

          "formatter" => "%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n",

          "filter-spec" => "substituteAll(JBAS\",\"EAP\")\"",

          "autoflush" => undefined,

          "target" => undefined

      }

       

      another try with:

       

      [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter-spec,value="any(match("JBAS.*"),not(match("ARJUNA.*")))")

      {

          "outcome" => "failed",

          "failure-description" => "JBAS014749: Operation handler failed: Expected string next in filter expression",

          "rolled-back" => true

      }

       

      ModelNode from debug :

      {

          "level" => "INFO",

          "enabled" => undefined,

          "encoding" => undefined,

          "formatter" => "%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n",

         "filter-spec" => "any(match(JBAS.*\"),not(match(\"ARJUNA.*\")))\"",

          "autoflush" => undefined,

          "target" => undefined

      }

       

      it seems like they lost one " just before JBAS, and then the failure described occured.

       

      Is it a bug? or I used the wrong way to configure it?