Exception: Pushing object second time
Posted: Mon 27 Nov 2006 10:38
Hallo
The following exception showed up two times already within our application:
Exception: System.InvalidOperationException
Message: Pushing object second time
Source: CoreLab.MySql
at CoreLab.Common.DbConnectionInternal.b(Object A_0)
at CoreLab.Common.DbConnectionPoolGroup.a(DbConnectionPool A_0)
at CoreLab.Common.DbConnectionPoolGroup.b(Object A_0)
We use the following software:
WindowsXP SP2
CorLab MySQLDirect .NET Data Provider Professional version 2.80.10 (01.11.05)
Mysql-4.0.21-win
.net framework 1.1
We are developing with Visual Studio .Net 2003 in C#
Your component is working in a big material handling system where the described error occurs. We are not able to reproduce the error in our office.
However, the exception occurs during a timer event in your code while we are not doing anything with the database. The exception does not seem to be an exception from .NET classes but from your classes.
Your help is highly appreciated as we are dealing with a very expensive production system that does not run stable.
Regards, Michael
The following exception showed up two times already within our application:
Exception: System.InvalidOperationException
Message: Pushing object second time
Source: CoreLab.MySql
at CoreLab.Common.DbConnectionInternal.b(Object A_0)
at CoreLab.Common.DbConnectionPoolGroup.a(DbConnectionPool A_0)
at CoreLab.Common.DbConnectionPoolGroup.b(Object A_0)
We use the following software:
WindowsXP SP2
CorLab MySQLDirect .NET Data Provider Professional version 2.80.10 (01.11.05)
Mysql-4.0.21-win
.net framework 1.1
We are developing with Visual Studio .Net 2003 in C#
Your component is working in a big material handling system where the described error occurs. We are not able to reproduce the error in our office.
However, the exception occurs during a timer event in your code while we are not doing anything with the database. The exception does not seem to be an exception from .NET classes but from your classes.
Your help is highly appreciated as we are dealing with a very expensive production system that does not run stable.
Regards, Michael