Partial Instrumentation in COM+

• 
  Unfortunately, I don't fully understand what you mean. A screen shot of:
  
  ANTS showing the call tree +
  ANTS showing the method grid results
  
  will be very helpful.
  
  Thanks!

  Chris.Allen January 31, 2012 06:40

  - 0 +
• 
  The architecture is as follows:
  
  Client -> COM+ Package
  
  In my scenario the client will do 1 call to COM+.
  
  Internally inside COM+, the called component will make many calls (37) to a main business component. During my instrumentation, only 1 or 2 calls (even 0 sometimes) are captured.
  
  Extra info:
  - Type of instrumentation: Method-level timings; all methods (faster)
  - My client is a Windows service
  - Code is release version
  - No PDB files deployed
  - I have often "Interop.SEHException" logged by the profiler at the beginning of the execution (but don't know what this means)

  ChristopheS January 31, 2012 08:16

  - 0 +
• 
  Sounds like frustratingly, 'one-of-those-things'. i.e. instrumenting code can interfere with the usual operation (it can reveal otherwise-hidden race-conditions, change thread-scheduling order, change permissions and lead to accessviolations etc).
  
  Does running in sampling mode give you more 9if less detailed) information?
  
  You may find running the profiler *explicitly* as administrator helps. Otherwise, if you wanted we would analyse a memory dump and try to understand the part ANTS is playing in any exceptions...

  Chris.Allen February 01, 2012 08:06

  - 0 +

Add comment

Please sign in to leave a comment.