You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Nicko Cadell (JIRA)" <ji...@apache.org> on 2006/03/27 00:31:18 UTC
[jira] Created: (LOG4NET-73) ADONetAppender.ActivateOptions()
database Connection Leak is called multiple times
ADONetAppender.ActivateOptions() database Connection Leak is called multiple times
----------------------------------------------------------------------------------
Key: LOG4NET-73
URL: http://issues.apache.org/jira/browse/LOG4NET-73
Project: Log4net
Type: Bug
Components: Appenders
Versions: 1.2.9
Reporter: Nicko Cadell
Assigned to: Nicko Cadell
ADONetAppender.ActivateOptions() calls InitializeDatabaseConnection. This method does not check if the m_dbConnection is already initialised. If it is initialise then it will beleaked.
Update InitializeDatabaseConnection to check and close the connection if not null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (LOG4NET-73) ADONetAppender.ActivateOptions()
leaks database connection when called multiple times
Posted by "Nicko Cadell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/LOG4NET-73?page=all ]
Nicko Cadell resolved LOG4NET-73:
---------------------------------
Fix Version: 1.2.10
Resolution: Fixed
Added code to cleanup the connection and command members if the InitialiseDatabaseConnection method is called multiple times.
> ADONetAppender.ActivateOptions() leaks database connection when called multiple times
> -------------------------------------------------------------------------------------
>
> Key: LOG4NET-73
> URL: http://issues.apache.org/jira/browse/LOG4NET-73
> Project: Log4net
> Type: Bug
> Components: Appenders
> Versions: 1.2.9
> Reporter: Nicko Cadell
> Assignee: Nicko Cadell
> Fix For: 1.2.10
>
> ADONetAppender.ActivateOptions() calls InitializeDatabaseConnection. This method does not check if the m_dbConnection is already initialised. If it is initialise then it will beleaked.
> Update InitializeDatabaseConnection to check and close the connection if not null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (LOG4NET-73) ADONetAppender.ActivateOptions() leaks
database connection when called multiple times
Posted by "Nicko Cadell (JIRA)" <ji...@apache.org>.
[ 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 Leak is called multiple times)
> ADONetAppender.ActivateOptions() leaks database connection when called multiple times
> -------------------------------------------------------------------------------------
>
> Key: LOG4NET-73
> URL: http://issues.apache.org/jira/browse/LOG4NET-73
> Project: Log4net
> Type: Bug
> Components: Appenders
> Versions: 1.2.9
> Reporter: Nicko Cadell
> Assignee: Nicko Cadell
>
> ADONetAppender.ActivateOptions() calls InitializeDatabaseConnection. This method does not check if the m_dbConnection is already initialised. If it is initialise then it will beleaked.
> Update InitializeDatabaseConnection to check and close the connection if not null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira