Comments
Sort by recent activity
This COM+ server is not one .Exe file. It is a collection of .Dlls that run under DllHost.exe. Under the Windows component services activation properties, this server is identified as a COM+ application. Many of these Dlls are loaded dynamically on demand. Can Ants Profiler track the memory of a unit of components such as this?[/img] / comments
This COM+ server is not one .Exe file. It is a collection of .Dlls that run under DllHost.exe. Under the Windows component services activation properties, this server is identified as a COM+ applic...
Hi,
Ants starts the client app. (which makes the request to the COM+ component - which gets it to load the .NET modules) in the debug environment and will produce results in Ants there. But using the same procedure to run a memory allocation profile in the release environment produces the log file shown in the earlier reply and the error about not having loaded the .NET runtime.
The COM+ service is listed in Ants and I select it, and I browse to the installed client, but after executing some of the client functionality, the results are not gathered.
Should I run the client app manually rather than let Ants do it? Or is there another way to start a client that uses a COM+ server?
regards,
albel / comments
Hi,
Ants starts the client app. (which makes the request to the COM+ component - which gets it to load the .NET modules) in the debug environment and will produce results in Ants there. But using t...
Hi,
I have been trying to get Ants to attach to the COM+ service to see its memory. I tried a few other approaches that did not work.
Does this log file tell you which direction to go to get the service to load the .Net framework when its is run in conjunction with Ants 3? Let me also know if there is a way to get more verbose logging from Ants Profiler 3.
Below is output in the log that it creates on the production virtual machine.
Regards,
1/11/2008 3:44:24 PM ANTSProfilerLog initialized
1/11/2008 3:44:24 PM PID = 4044
1/11/2008 3:44:24 PM Log file name = ANTSProfilerLog4044.txt
1/11/2008 3:44:24 PM OS version = Microsoft Windows NT 5.1.2600 Service Pack 2
1/11/2008 3:44:24 PM Machine name = ABELINSKAS-IBM
1/11/2008 3:44:24 PM User name = abelinskas
1/11/2008 3:44:24 PM PARAMHOST - Listening on port 8084
1/11/2008 3:44:24 PM PARAMHOST - Listening on port 8084, channel registered
1/11/2008 3:44:26 PM EditProjectClosingWizard start
1/11/2008 3:44:26 PM EditProjectClosingWizard start
1/11/2008 3:44:26 PM About to show wizard
1/11/2008 3:44:42 PM Wizard dialog returned
1/11/2008 3:44:46 PM UI Start profiling
1/11/2008 3:44:46 PM ENGINE - Core2.dll found in regisry
1/11/2008 3:44:54 PM ENGINE Start profiling memory of COM+ application IdpSvc
1/11/2008 3:44:54 PM ENGINE The profiler is enabled
1/11/2008 3:44:54 PM TRANSFER - Waiting for pipe connection from core
1/11/2008 3:45:51 PM UI Take snapshot
1/11/2008 3:45:51 PM ENGINE Start get memory results
1/11/2008 3:45:51 PM TRANSFER - Not connected so returning last set of results
1/11/2008 3:46:58 PM UI Stop profiling
1/11/2008 3:46:58 PM ENGINE Stopping profiler
1/11/2008 3:46:58 PM ENGINE Closing profiling session
1/11/2008 4:11:42 PM ENGINE Closing profiling session / comments
Hi,
I have been trying to get Ants to attach to the COM+ service to see its memory. I tried a few other approaches that did not work.
Does this log file tell you which direction to go to get the se...
Hi,
I am trying to profile the memory usage of the production version of a COM+ component on a production machine. I am not really interested in the performance profile of the COM+ component. The error message reported by Ants Profiler 3, the "The COM+ Svc has not loaded the .NET Framework. Please check that Svc is a .NET application..." message included in my earlier post, is generated when I try a memory profile session with Ants Profiler 3.
I guess my next question is: do I need a debug version of the COM+ component to get memory profile results with Ants Profiler 3?
Regards,
albel / comments
Hi,
I am trying to profile the memory usage of the production version of a COM+ component on a production machine. I am not really interested in the performance profile of the COM+ component. The ...
Hi,
Two observations suggest the COM+ component didn't crash:
- The application that calls the COM component ran to completion, using the COM component during database processing. If the COM component didn't work, nothing would have been written to the database (3000 records were written).
- There were no Application or System Events in the Event viewer related to either Ants Profiler, or my application.
Does Ants Profiler 3 itself have any logging mechanism that could shed more light on any problems it has during a memory profile session?
Regards,
albel / comments
Hi,
Two observations suggest the COM+ component didn't crash:
- The application that calls the COM component ran to completion, using the COM component during database processing. If the COM compon...