[
https://issues.jboss.org/browse/AS7-4953?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat resolved AS7-4953.
---------------------------------
Resolution: Won't Fix
This is an oversight, but it is not possible to fix it [it would require dropping the
default value I think]. The default pattern value is set to the "common"
pattern, which is a valid value for the regular access log, but not for the extended one
which uses a totally different syntax. There's no reason to use the extended access
log if you're not going to actually use it, anyway, use the normal access log
instead.
So unless you have an idea with hopefully a patch for it, it won't be fixed.
Extended Access Log doesn't work if you don't provide
patteren
--------------------------------------------------------------
Key: AS7-4953
URL:
https://issues.jboss.org/browse/AS7-4953
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.1.Final
Environment: Java 1.7.04
Windows 7 x64
Reporter: Tomaz Zupan
Assignee: Remy Maucherat
Labels: access, extended, log, web
If in configuration file in subsystem=urn:jboss:domain:web:1.1 / virtual-server section
you add:
{code:xml}
<access-log extended="true">
<directory path="logs" relative-to="something"/>
</access-log>
{code}
there is the following error in console when JBoss is started:
{code}09:51:00,713 ERROR [org.apache.catalina.valves.ExtendedAccessLogValve] unable to
decode with rest of chars starting: %h{code}
and access logging doesn't work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira