I have an n-tier .NET enterprise application that is having some issues.
I'm utilizing three tiers.
Presentation - ASP.NET web application
Business - .NET class library using Enterprise Services and COM+
Data - SQL server 2000
The presentation instantiates components from the business tier, does what
it needs to do and then disposes of the object using .dispose. Event
tracking is enabled on the COM+ app components, and all objects show 0
instances being held after the method called is finished executing.
The issue is that when the com+ app in the business tier is first called, a
dllhost.exe is started with a memory allocated around 15,000K. The first
request to the create an instance causes the memory to jump to 19,000K and
then with every additional call to the component, the dllhost.exe increases
in memory until the server falls over... Its as if the memory allocated for
the objects in com+ are never being released once instantiated.
Does anyone have any suggestions?
Thank you.
T
posthumecaver - 26 Aug 2003 14:53 GMT
Are you calling the dispose methods of the serviced components.
Btw, if you are not using the Transaction Support of the COM+ why are u
using with ASP.NET.
ASP.NET Application domains are already given you all the benefits of the
COM+ except transaction support and Object Pooling.
> I have an n-tier .NET enterprise application that is having some issues.
>
[quoted text clipped - 19 lines]
> Thank you.
> T
posthumecaver - 26 Aug 2003 14:56 GMT
Sorry stupid answer,
I already saw that you are using the dispose method.
What happens you force the Garbage Collector to run.
I guess it is gc.Collect
> I have an n-tier .NET enterprise application that is having some issues.
>
[quoted text clipped - 19 lines]
> Thank you.
> T