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

COM+ System slowdown!!

COM+ System slowdown!!

COM+ System slowdown!!

we have a complus application that has a few hundred components in it..  the system seems to work fine to start with but as time goes on it gets slower and slower.. and eventualy grindes to a halt..  restarted COM+ components sorts the problem for a while but quickly the problem returns..  a reboot stops the problem for longer..

we are getting this problem at least once or twice a day!!

the application is running on w2k with sp3, and it connects to SQL server 2000.. we've checked the obvious things about not enough sql connections..etc or the application holding open too many objects, but this doesn't seem to be the case.. the CPU usage is very very low so its not something stuck in a loop or anything like that..

there is no high load.. the most users that are ever on is about 15!

anybody experienced anything like this??

any ideas?


RE: COM+ System slowdown!!

Some things to try/check:
- is your com+ package set to be a server or library process?  (activation tab); in most cases you should use server so that it runs in a dedicated process as opposed to library which runs it within the creators process

- do all your public middle tier methods dispose of the transaction object both on success and failure (objctx.setcomplete at end of method, and objctx.setabort in error handler)-even for non transactional methods (lookups etc) this is very important because both setcomplete and setabort not only "vote" yes/no for the transaction to proceed but they also clean up the memory associated with that particular objectcontext

- what version of ADO are you using?  We discovered in ADO 2.5 that connections do not necessarily get closed even if you call cn.close and set your connection object to nothing (maybe run SQL Profiler and watch your connection usage)

- in com+ on the advanced tab for your package, do you have an idle timeout specified for your app so that it does not stay running when idle?

Hope this helps,
Good luck!

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