Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-4644

enabling access-log for virtual server is not effective before server reload but CLI does not require that

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 10.0.0.Alpha3
    • 9.0.0.CR1
    • Web (Undertow)
    • None
    • Hide

      Add access-log for e.g. default vhost:

      [standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=default-host/setting=access-log:add()
{"outcome" => "success"}

      (no server reload required)
      Do some request on server... no logged data...
      Perform server reload...

      [standalone@localhost:9990 setting=access-log] reload

      do some request on server... requests are logged now...

      Show
      Add access-log for e.g. default vhost: [standalone@localhost:9990 /] /subsystem=undertow/server= default -server/host= default -host/setting=access-log:add() { "outcome" => "success" } (no server reload required) Do some request on server... no logged data... Perform server reload... [standalone@localhost:9990 setting=access-log] reload do some request on server... requests are logged now...

      When access-log is enabled for virtual host via CLI it does not want to perform server reload. But until server reload is executed logging is not enabled. When server reload is performed then logging works OK.

              sdouglas1@redhat.com Stuart Douglas (Inactive)
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: