MTX.EXE

Greetings,

Using dbview free 1.1711 in our tests we see multiple MTX.EXE running and eating memory.

Any ideas how to solve this?

Thanks

-Costas Zividis

Hi Costas,

When you register any dll in MTS (Microsoft Transaction Server), this happens.
What happens is that for every copy of the dll that is loaded into memory,
a copy of the MTX.EXE process is spawned and controls the execution of that
dll. When the sessions end / timers run out, that process will be terminated
and the memory returned to the pool. MTS doesn't delete the in-process dll
threads immediately upon termination of the ASP session, because another
session will probably come along in the next few sessions to request the same
dll. After a period of time of inactivity, it's finally released.

There are no "memory leaks" in the ASP-db software (any version). We've
tested it extensively. We have a version running on a production server
with a 4 month "uptime" and it hasn't eaten one extra byte of memory yet!

Hope this helps,
John



------------
Costas Zividis at 12/16/99 7:31:52 AM


Greetings,

Using dbview free 1.1711 in our tests we see multiple MTX.EXE running and eating memory.

Any ideas how to solve this?

Thanks

-Costas Zividis

Hello Jon,

Thanks for the reply. The problem is that a copy of mtx.exe is always active after the first time we try to run a site using aspdb. Multiple mtx.exe processes are started but ended as well. Is it normal for one to stay active forever, no matter what?

I'm sure Aspdb doesn't harm our server for any reason :)

-Costas



------------
John at 12/16/99 10:25:01 PM

Hi Costas,

When you register any dll in MTS (Microsoft Transaction Server), this happens.
What happens is that for every copy of the dll that is loaded into memory,
a copy of the MTX.EXE process is spawned and controls the execution of that
dll. When the sessions end / timers run out, that process will be terminated
and the memory returned to the pool. MTS doesn't delete the in-process dll
threads immediately upon termination of the ASP session, because another
session will probably come along in the next few sessions to request the same
dll. After a period of time of inactivity, it's finally released.

There are no "memory leaks" in the ASP-db software (any version). We've
tested it extensively. We have a version running on a production server
with a 4 month "uptime" and it hasn't eaten one extra byte of memory yet!

Hope this helps,
John

Hi Costas,

Yes, it's perfectly normal for that MTX.EXE process to start after the first
component is activated and stay in memory from then on. Apparently MTS
uses that MTX thread to marshall the use of the other in-process components,
and once activated, it remains resident for control of future loads.

Thanks!
John


------------
Costas Zividis at 12/17/99 3:09:09 AM


Hello Jon,

Thanks for the reply. The problem is that a copy of mtx.exe is always active after the first time we try to run a site using aspdb. Multiple mtx.exe processes are started but ended as well. Is it normal for one to stay active forever, no matter what?

I'm sure Aspdb doesn't harm our server for any reason :)

-Costas



------------
John at 12/16/99 10:25:01 PM

Hi Costas,

When you register any dll in MTS (Microsoft Transaction Server), this happens.
What happens is that for every copy of the dll that is loaded into memory,
a copy of the MTX.EXE process is spawned and controls the execution of that
dll. When the sessions end / timers run out, that process will be terminated
and the memory returned to the pool. MTS doesn't delete the in-process dll
threads immediately upon termination of the ASP session, because another
session will probably come along in the next few sessions to request the same
dll. After a period of time of inactivity, it's finally released.

There are no "memory leaks" in the ASP-db software (any version). We've
tested it extensively. We have a version running on a production server
with a 4 month "uptime" and it hasn't eaten one extra byte of memory yet!

Hope this helps,
John