[
https://issues.jboss.org/browse/WFLY-2524?page=com.atlassian.jira.plugin....
]
Dominik Pospisil commented on WFLY-2524:
----------------------------------------
The issue seems to be in ClassLoaderLogContextSelector. The LogContextSelector scans
caller stacktrace to see if there is a class for which a classloader has a registered
logging context. In other words it scan a stacktrace for a class from given deployment. In
case of JSP page, there is no such class as the JSP servlet handler is loaded using custom
classloader. Posible solution is to scan for parent CL as well.
logging-profile works for a servlet, but doesn't for a JSP
----------------------------------------------------------
Key: WFLY-2524
URL:
https://issues.jboss.org/browse/WFLY-2524
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: 8.0.0.Beta1
Reporter: Osamu Nagano
Assignee: James Perkins
Attachments: logone.zip
Suppose the following logging-profile has been set in logging subsystem, and a web app
has a proper entry in its MANIFEST.MF ({{Logging-Profile: logone}}). Then all messages
via "com.example.logone" logger should go into a file, logone.log. It does so
with a logger got in a servlet, but it doesn't work a logger got in a JSP.
{code}
<logging-profiles>
<logging-profile name="logone">
<file-handler name="logone">
<level name="INFO"/>
<file relative-to="jboss.server.log.dir"
path="logone.log"/>
</file-handler>
<logger category="com.example.logone">
<level name="INFO"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="logone"/>
</handlers>
</root-logger>
</logging-profile>
</logging-profiles>
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)