Pushing object second time.

Pushing object second time.

Postby LarsOberg » Sun 26 Nov 2006 18:36

We are getting the exception below every now and then when using CoreLab MySQLDirect.NET:

System.InvalidOperationException was unhandled
Message="Pushing object second time."
Source="CoreLab.MySql"
StackTrace:
at CoreLab.Common.DbConnectionInternal.b(Object A_0)
at CoreLab.Common.DbConnectionPoolGroup.a(DbConnectionPool A_0)
at CoreLab.Common.DbConnectionPoolGroup.a(Object A_0)
at System.Threading._TimerCallback.TimerCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._TimerCallback.PerformTimerCallback(Object state)

It is intermittent and seemingly random. It happens maybe once or twice a week, but since it is a mission critical system that has to run 24x7, it is causing us quite a problem. The exception is generated from within the Corelab DLLs and there is no call-stack or anything else to give any hint as to what is causing it.

We are using MySQL Direct Version 3.20.9.0. The server is RH 3.x, MySQL 5.0.22. The environment is Visual Studio 2005 (C#). It is happening on more than one workstation.

We have not been able to find a way to reproduce it and the application where this is happening requires too complex an environment for us to send a sample application. Nevertheless, we need a solution urgently.

Please help.

Thanks,
Lars
LarsOberg
 
Posts: 41
Joined: Tue 11 Oct 2005 18:45

Postby Alexey » Mon 27 Nov 2006 07:49

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

Postby Michael G » Mon 27 Nov 2006 12:06

Hi Lars

We have the same problem with Version 2.80.10 (other thread). Please let me now if you have a solution.

Regards
Michael
Michael G
 
Posts: 3
Joined: Mon 27 Nov 2006 10:30

Postby Alexey » Mon 27 Nov 2006 12:13

Guys, please use MySQLDirect .NET 3.50.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby LarsOberg » Wed 06 Dec 2006 18:10

Alexy, et al.,

I upgraded to 3.50 as requested about a week ago. I have not seen the problem since, but it is a bit early to tell for sure yet. If I have the problem again, I will post here to let you know right away.

Thanks,
Lars
LarsOberg
 
Posts: 41
Joined: Tue 11 Oct 2005 18:45

Postby Alexey » Thu 07 Dec 2006 07:05

OK. If the problem won't occur, please make a post as well to confirm that it is absent in MySQLDirect .NET 3.50.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby LarsOberg » Thu 07 Dec 2006 17:13

Ok, but I'll give it a couple of weeks or so to make sure.
LarsOberg
 
Posts: 41
Joined: Tue 11 Oct 2005 18:45

Postby Alexey » Fri 08 Dec 2006 10:53

I see.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby LarsOberg » Mon 18 Dec 2006 03:58

I have now used the new version (3.50) for a few weeks and the problem seems to be handled.

I do have another problem instead, that I did not have with the previous version. I'll create a new thread for this.

Thanks,
Lars
LarsOberg
 
Posts: 41
Joined: Tue 11 Oct 2005 18:45

Postby Alexey » Mon 18 Dec 2006 08:24

OK, I'll take a look.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43


Return to dotConnect for MySQL