Anonymous | Login | Signup for a new account | 12-17-2024 08:33 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0002327 | [Resin] | minor | always | 01-14-08 09:12 | 02-13-08 15:25 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 3.1.4 | ||||||
Summary | 0002327: java.util.logging level override issue | ||||||||
Description |
(rep by John Franey) The code differences between 3.0.24 and 3.1.4 snapshot imply that this issue also exists in 3.1, so I've edited my question and resent it. Aside from innocuous changes to import statements, postconstruct annotation and comments, the three significant fixes are: a fix to jmx registration of the sublogger (LogConfig), a fix to use local handlers instead of super.log to publish log messages (EnvironmentLogger), and a fix to el variable evaluation. Added classes are AbstracRolloverLog, EnvironmentStream, RotateString, TimestampFilter. I don't think these differences will affect this issue. John J. Franey wrote: Here is an excerpt of my logging config in resin.conf: ... <host ...> <web-app ...> <log path="..." timestamp="..." format="..."> .... <logger name="com.corp" level="fine"> <logger name="com.corp.deep.package" level="info"/> .... </web-app> </host> .. The problem is that the loggers at or below com.corp.deep.package are writing out fine log messages. In a regular java app, if I configured logging in a logging.properties to something similar, fine log messages from com.corp.deep.package loggers would not be written out. |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |