Description of problem:
When enabling host resolution for access log there is no change at log records, so it seems that this setting is not effective at all.


Version-Release number of selected component (if applicable):
EAP 6.2.0.ER7, JBoss Web 7.2.2.Final-redhat-1, JBoss Application Server: Web Subsystem 7.3.0.Final-redhat-SNAPSHOT

How reproducible:
always

Steps to Reproduce:
0. default instalation of EAP with default config started as standalone
1. Enable access log with resolving disabled: /subsystem=web/virtual-server=default-host/access-log=configuration:add(resolve-hosts=false)
2. perform several web accesses at localhost:8080 or if you can, do external access to your public IP
3. check log at <eap-dir>/standalone/log/default-host and see that IP is in first field of each record.
4. Enable resolving: /subsystem=web/virtual-server=default-host/access-log=configuration:write-attribute(name=resolve-hosts,value=false)
5. again perform several web accesses the same way as in step 2)
6. check log again and check if hostname is in first field of each new record.


Actual results:
Resolving hostnames is not seem to work, there are only IPs in log.

Expected results:
Resolving hostnames works.


Additional info:
Since JBoss Web has very poor docs and is based on Tomcat, I found at
http://tomcat.apache.org/tomcat-7.0-doc/api/org/apache/catalina/valves/AccessLogValve.html where it says "Remote host name (or IP address if enableLookups for the connector is false)" for request hostname.
So I try to turn it on /subsystem=web/connector=http:write-attribute(name=enable-lookups,value=true)
and it starts to resolving hosts no matter what the value of resolve-host attribute is.