Pramod Jaiswal created LOG4NET-628:
--------------------------------------

             Summary: Log4net : WARN Exception while disposing cached 
connection object
                 Key: LOG4NET-628
                 URL: https://issues.apache.org/jira/browse/LOG4NET-628
             Project: Log4net
          Issue Type: Bug
          Components: Appenders
            Reporter: Pramod Jaiswal


Dear,

We are using log4net component in one of the C# project. When application is 
about to finish, suddenly below error message popups on the application console-

 

System.InvalidOperationException: Internal .Net Framework Data Provider error 1.

 

   at System.Data.ProviderBase.DbConnectionInternal.PrePush(Object expectedOwner

)

   at System.Data.ProviderBase.DbConnectionPool.PutObject(DbConnectionInternal o

bj, Object owningObject)

   at System.Data.ProviderBase.DbConnectionInternal.CloseConnection(DbConnection

owningObject, DbConnectionFactory connectionFactory)

   at System.Data.SqlClient.SqlConnection.CloseInnerConnection()

   at System.Data.SqlClient.SqlConnection.Close()

  at log4net.Appender.AdoNetAppender.DiposeConnection()

log4net:WARN Exception while disposing cached connection object

System.InvalidOperationException: Internal .Net Framework Data Provider error 1.

 

   at System.Data.ProviderBase.DbConnectionInternal.PrePush(Object expectedOwner

)

   at System.Data.ProviderBase.DbConnectionPool.PutObject(DbConnectionInternal o

bj, Object owningObject)

   at System.Data.ProviderBase.DbConnectionInternal.CloseConnection(DbConnection

owningObject, DbConnectionFactory connectionFactory)

   at System.Data.SqlClient.SqlConnection.CloseInnerConnection()

   at System.Data.SqlClient.SqlConnection.Close()

   at log4net.Appender.AdoNetAppender.DiposeConnection()

 

Could you please let me know why this error message is coming and how to avoid 
this error message on console screen as this issue is coming on PROD 
environment and our client has escalated this issue.

 

Thanks in advance for providing the solution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to