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 2004/04/02 00:46:11 UTC
DO NOT REPLY [Bug 27505] -
JDBCAppender: allow to use JNDI datasource
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27505>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27505
JDBCAppender: allow to use JNDI datasource
------- Additional Comments From clement.ong@shinetech.com 2004-04-01 22:46 -------
Hi Gino,
You're right that the JDBCAppender is not of production quality. This is the
second problem I discovered in this class. The first was when we were using an
old version of log4j which has the persistent major memory leak in the flush
method and the most recent memory leak due to stale connection. This parcular
problem is very subtle(which could be caused the firewall or a *database
restart or crash.*) as it's very hard to pinpoint where the memory leak is
occuring in.
In a J2EE environment it is ill advised to use file based logging destination
as it contravene the EJB specification rule. This is where JDBCAppender or
JMSType destination could be use.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org