×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

MTS and Oracle --Sessions at oracle not being killed

MTS and Oracle --Sessions at oracle not being killed

MTS and Oracle --Sessions at oracle not being killed

(OP)
Hi,
I am developing a COM+ application using VB which speaks to an oracle stored procedure running on a system(win 2000 server) where i have my MTS.I have installed oracle server 7.3 on a different system.The COM+ application Transaction property is not enabled and the application is working fine.
But the Oracle session is not being killed after each call that i make , even after i kill the Connection in my application.I am using Microsoft ODBC driver for oracle.
Can anybody help me.

Thanks in advance

Regards
Khan

RE: MTS and Oracle --Sessions at oracle not being killed

When a component under the control of a Connection Pool Manager (CPM) like MTS asks for a connection then releases it the connection is not really released.  The CPM hold on to the connection incase another object requests a connection with the same profile (Same UserID,Password, Database, etc) and hands them the already connected connection thus speeding up database access.  Normally this is just fine.  MTS will slowly drop connections if no objects are requesting them or if it is getting more requests for connections with a different profile where it might then purposely close down a connection to open it back up with a the new profile.

Hope this helps

RE: MTS and Oracle --Sessions at oracle not being killed

When a component under the control of a Connection Pool Manager (CPM) like MTS asks for a connection then releases it the connection is not really released.  The CPM hold on to the connection incase another object requests a connection with the same profile (Same UserID,Password, Database, etc) and hands them the already connected connection thus speeding up database access.  Normally this is just fine.  MTS will slowly drop connections if no objects are requesting them or if it is getting more requests for connections with a different profile where it might then purposely close down a connection to open it back up with a the new profile.

Hope this helps

Oh look here to see a similar explantion I've given

Thread330-327996

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close