[ http://issues.apache.org/jira/browse/LOG4NET-73?page=all ]
Nicko Cadell updated LOG4NET-73:
Summary: ADONetAppender.ActivateOptions() leaks database connection when
called multiple times (was: ADONetAppender.ActivateOptions() database
Connection
Author: nicko
Date: Mon Mar 27 04:57:23 2006
New Revision: 389130
URL: http://svn.apache.org/viewcvs?rev=389130view=rev
Log:
Fix for LOG4NET-73. Added code to cleanup the connection and command objects
that are stored in members if the InitializeDatabaseConnection method is called
multiple
Author: nicko
Date: Mon Mar 27 06:10:19 2006
New Revision: 389152
URL: http://svn.apache.org/viewcvs?rev=389152view=rev
Log:
Fix for LOG4NET-72. Moved String.Format call into separate class
SystemStringFormat. This class holds the format string and arguments and only
performs the String.Format
[ http://issues.apache.org/jira/browse/LOG4NET-70?page=all ]
Nicko Cadell resolved LOG4NET-70:
-
Resolution: Fixed
Check in to update referenced dll name has fixed this issue.
CoreDll.dll referenced with different capitalisation
This is by design, but it is subtle behaviour.
The configuration attributes are loaded from the first assembly to call
log4net.LogManager.GetLogger. Configuration attributes on other
assemblies loaded into the process are ignored. What this basically
means is that you main assembly should get a
[ http://issues.apache.org/jira/browse/LOG4NET-69?page=all ]
Nicko Cadell resolved LOG4NET-69:
-
Fix Version: 1.2.10
Resolution: Fixed
This is fixed and i have added a test to ensure that malformed format strings
don't leak exceptions.
Change MemoryAppender member variables to protected
---
Key: LOG4NET-74
URL: http://issues.apache.org/jira/browse/LOG4NET-74
Project: Log4net
Type: Improvement
Components: Appenders
Versions: 1.2.9
