Bug 1027274

Description of problem:
When enabling access log for virtual server through CLI no reload is required, but accesss logging is not active until server is reloaded.


Version-Release number of selected component (if applicable):
EAP 6.2.0.ER7

How reproducible:
always


Steps to Reproduce:
1. Get jboss-eap-6.2.zip and extract to get clean installation

2. Start server (standalone mode) and connect to CLI

3. Check log dir, <dist-dir>/standalone/log - no subdirectory exists

4. Enable access log in CLI:
/subsystem=web/virtual-server=default-host/access-log=configuration:add

5. Check log dir, <dist-dir>/standalone/log - no subdirectory exists

6. Perform web access several times by, ie. repeatedly go to http://localhost:8080

7. Wait few seconds (a minute to be more sure) for write buffer to be flushed

8. Check log dir again, still no subdir for virtual server there and no access log files there.



Actual results:
CLI prints {"outcome" => "success"} ie. no reload required 
and access logging is not active until server is reloaded, ie. no dir "default-host" in log directory and no files in there.

If reload is performed right after step 4), then in step 5) there exists subdirectory "default-host" with empty access log file and logging is active, ie. you can see modified file after web access.


Expected results:
Either reload-required flag is set after adding access log, or access logging is active immediately after activation.