By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,350 Members | 1,228 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,350 IT Pros & Developers. It's quick & easy.

Connection Issue - .NET and Oracle

P: n/a
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.

Nov 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
You will need to post some code and where the error message is happening.

bill
"Rig76" <ri***@hotmail.com> wrote in message
news:11**********************@g44g2000cwa.googlegr oups.com...
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.

Nov 19 '05 #2

P: n/a
Hi Bill,
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 your reply

Nov 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.