You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2003/02/19 05:54:40 UTC
DO NOT REPLY [Bug 16998] -
JDBCAppender leaks memory
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16998>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16998
JDBCAppender leaks memory
mwomack@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From mwomack@apache.org 2003-02-19 04:54 -------
This is a duplicate of earlier reported bug #14827, which will be addressed in
the v1.2.8 release. If you are interested in improving JDBCAppender, I urge
you to become involved with its development on the log4j-dev email list.
Thanks.
*** This bug has been marked as a duplicate of 14827 ***
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org