Thanks Jaikiran,

The documentation you pointed me at, helped me a lot.

I finally did manage to get the correct IP by setting the Valve in jboss-web.xml.

However since now in JBoss 7 this valve is configured per deployment application and not at server level, setting <access-log/> in standalone.xml do not make the acces log files use remote IP. The valve here is only doing its job for the deployed app.

To resolved this issue I removed <access-log/> in standalone.xml file and I added the corresponding acces log valve in my jboss-web.xml.

For those interested, here is the final version of jboss-web.xml that we are using:

{code:xml}
<jboss-web>
    <valve>
        <class-name>org.apache.catalina.valves.RemoteIpValve</class-name>
        <param>
            <param-name>protocolHeader</param-name>
            <param-value>x-forwarded-proto</param-value>
        </param>
    </valve>
    <valve>
        <class-name>org.apache.catalina.valves.AccessLogValve</class-name>
        <param>
            <param-name>prefix</param-name>
            <param-value>http_access_log.</param-value>
        </param>
        <param>
            <param-name>suffix</param-name>
            <param-value>.log</param-value>
        </param>
        <param>
            <param-name>pattern</param-name>
            <param-value>%h %l %u %t "%r" %s %b %{User-Agent}i %{JSESSIONID}c</param-value>
        </param>
        <param>
            <param-name>directory</param-name>
            <param-value>host</param-value>
        </param>
        <param>
            <param-name>resolveHosts</param-name>
            <param-value>false</param-value>
        </param>
    </valve>
</jboss-web>
{code}

However there is one little drawback with this AccessLogValve, it uses the system property catalina.base as the root directory for access log when the given directory is relative.

Since this property is not set the directory gets created where jboss is started...

I think that this valve needs to evolve to use jboss.home.dir instead.