https://issues.apache.org/bugzilla/show_bug.cgi?id=44908
Mark Thomas <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #2 from Mark Thomas <[EMAIL PROTECTED]> 2008-05-01 15:42:19 PST ---
There might be a bug here but...
log4j isn't provided as part of the standard TC4 distro so the
LoggerConfigurationException is understandable.
The reason you are seeing this is that Tomcat tries to log web-app related
messages to the logger(s) associated with the web-app. What you are seeing is a
side-effect of this.
There have been bugs in this area in the past, usually memory leaks related to
class loaders not being properly released, and it wouldn't surprise me if a few
more issues of that type were still in TC4. That said, I don't think this
falls into that category.
There are also many, many pages on the web documenting some horrible
experiences people have have with logging frameworks and the class loader
structure of a typical Servlet container. This has been improved in later
versions but the changes are way to invasive to port back to the TC4 branch.
In short, small bugs in the logging will get fixed whereas issues that need
architectural changes will not.
All that said, so far this issue looks like a configuration error to me.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
