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!
  • Students Click Here

*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

Problem with mtx.exe (Memory)

Problem with mtx.exe (Memory)

Problem with mtx.exe (Memory)

Hi there,

I'm having lots of trouble with mtx ... Can anyone tell me if it's normal to have several mtx processes. I'm having problems with memory (Out of memory) and when I go to the task manager I can see 4 instances of mtx hanging (one with 4MB,two with 11, one 25MB).
I aprecciate some help.

Thanx in advance
Paulo Silva
Lisbon - Portugal

RE: Problem with mtx.exe (Memory)


The count of MTX.exe's will depend on the number of packages you have.  The formula is MTX_Count = Package_Count + 1.  The spare MTX.exe is a sort of "traffic cop" that helps direct traffic.

The size of the package-oriented MTX.exe will vary (read: will grow), and will generally be bigger than the relatively-stable traffic cop MTX.exe.  I have seen some of them over 100M in size, and still functioning.

One other thought: if your MTX_Count is higher than the formula above indicates, then yes, there's a definite problem.  Unfortunately, I don't know what sort of problem, or how to solve it.

Hope this helps,

RE: Problem with mtx.exe (Memory)

It is better to have your components stateless.Which means that you should call SetComplete/SetAbort once you finish job.
This way you will make the system more extensible and the memory can be used more effectively.


Long live of freedom!

RE: Problem with mtx.exe (Memory)

One of the problems I have found is ending processes on mtx.exe's where you really don't know which one to kill. If you have multiple components on your server it's a guessing game when you want to end a process. Usually you look at CPU time and memory, but Microsoft has a cool tool called Tlist which will list the dll's that an mtx.exe is using. That way you can shutdown a component or monitor certain components if you are having a difficulty. Here's the article ID. Bookmark it, it's real useful.

Article ID: Q221143

RE: Problem with mtx.exe (Memory)

     PView.exe (Process Viewer) which ships with Visual Studios will do the same thing. It will allow you to see all binary files (*.exe, *.dll, *.ocx) that are being used by any process space.

- Jeff Marler

RE: Problem with mtx.exe (Memory)

One more comment . . .
     What Zallen said is not only true, it is a must. You must ensure that all of your components within MTS or Component Services are stateless. This is VERY important for scalability.

- Jeff Marler

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