Thread Problem in COM+

[petersonfv]

Hello...
I hope you help me.
I have a dll installed at COM+ in a Windows2000 Server SP2.
The clients applications (written in vb6) have an application proxy that connects it.
This dll has several classes and functions. But, there is a simple function that has causing problems.
When it is executed, the component stay in memory and does not return. After, the others components does not work more in all clients, and I need to shutdown the Application Server.
This function call a simple update stored procedure in SQL Server 2000. I use ADO and Mdac 2.7.
The vb project has unattend execution and retained in memory options checked.
I thought that it is a thread problem.
What do you think?

 

[SemperFiDownUnda]

is the class not in a Component Services Transaction and is the function hitting a database lock thus just blocking waiting for the resource to free up?

If the class is in a component Services transaction then Component Services will time it out where ADODB will allow you to block indefinately.

But the underlying problem indicates maybe you have some application logic problems they maybe due to something not being designed properly to be scaleable.

 

[petersonfv]

Hello.
This class uses an ADODB command to execute a stored procedure that update one row. The MTSTransaction Mode is 3-UsesTransactionandm and I controle the Transaction with ADO (cnn.BeginTrans, cnn.RollBackTrans).
I tested inside VB Project and works fine, the problem happens in COM+. After, I tested when there was only one client machine connected in COM+, and the problem happens again. I thought that there was not lock database.
I supposed that was the call function in application, or a confict name function. The Server has several COM+ Application Server, but connect other database.
What do you think?