microsoft.public.dotnet.framework.aspnet

R

Rig76

I'm having a very strange issue with an application I'm building. The
applicaiton has multiple users, each with their own connection to the
database. However, when one of these connections closes then all the
other users connections seem to close.

This is most obviously seen when I'm writing a rather large chunk of
data with connection A. Then connection B comes in to the application
and grabs a small piece of data. Of course, during execution,
connection B will cllose itself after getting what it needs. It's at
this point that connection A gets the following message "Connection
must be open for this operation" while writing its next piece of data.

If any could help me with this, it would be greatly appreciated.
 
S

Scott Allen

Hi Rig:

Could you share some code? It sounds as if connections are being
improperly handled in your code.
 
A

A B

Hi Scott,
I was able to get this solved. What was happening was that I was
declaring my connection object in a VB .NET module. The object wasn't
created or closed in that same module but it still caused the connection
object to be shared despite that each user has their own unique login.
Since the connection object was shared, when Connection B called closed,
it ended up closing the connection on everyone.

Thanks for you reply.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,484
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top