Exception: Pushing object second time

Exception: Pushing object second time

Postby Michael G » Mon 27 Nov 2006 10:38


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)
.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
Michael G
Posts: 3
Joined: Mon 27 Nov 2006 10:30

Postby Alexey » Mon 27 Nov 2006 10:53

Try to reproduce the error with the latest version of MySQLDirect .NET.
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby reusch » Mon 27 Nov 2006 12:44


our software controls a production system in a pharmaceutical environment. It is not so easy to switch from one version to another (there has a lot of paperwork to be done for QS reasons). For this reason we want to know if it is just an assumption and y try that this error does not occur anymore or if the problem is fixed definitely.
Are the versions compatible or do we have to make changes to our program? Are there workarounds (e.g. deactivate the function in which the exception occurs?) Is it possible for you to fix the problem in 2.8.10? Are there experiences with the new version in productive environments?

Best regards,

Posts: 2
Joined: Fri 24 Nov 2006 16:40

Postby Alexey » Tue 28 Nov 2006 07:46

I understand you. But... We have never been reported about this error, so i cannot say for sure that it is definitely fixed. Also I am not able to try to reproduce it with any version, because you say it is intermittent. If you could localize the problem and provide us with the circumstances which produce this issue, it would be helpful for both of us.
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Return to dotConnect for MySQL