-
Bug
-
Resolution: Done
-
Major
-
None
-
None
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.
<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>
- blocks
-
WFLY-3857 Add JSP logging profile test
-
- Closed
-
- is related to
-
WFLY-1814 Static loggers in modules could be created on wrong log context if logging profiles are used
-
- Closed
-
-
WFCORE-100 Upgrade JBoss Log Manager from 1.5.2.Final to 2.0.0.Beta1
-
- Resolved
-
- relates to
-
LOGMGR-111 ClassLoaderLogContextSelector should optionally include parent CL for context scanning
-
- Resolved
-