trace of thought (Scott Colestock) - Knowing which BTSNTSvc.exe to attach to...

Thursday, May 12, 2005

Knowing which BTSNTSvc.exe to attach to...

Andy Morrison wrote about a technique for identifying the correct host instance to attach to when debugging components associated with orchestrations.

A potentially easier solution is to keep perfmon running with the counter shown below (BizTalk:Messaging/ID Process - all instances.) The counter values will update every time a host instance recycles. The Debug-Processes dialog in Visual Studio will show you (and allow you to sort by) process IDs to make this easy.

Then put PerfMon in "report view" to easily see process IDs by host instance:

Thursday, May 12, 2005 9:32:41 AM (Central Standard Time, UTC-06:00)

Comments [3] -
BizTalk Insights

Thursday, May 12, 2005 9:45:28 PM (Central Standard Time, UTC-06:00)

Andy suggests an external tool - see http://blog.magenic.com/andym/archive/2005/05/12/759.aspx
You could also wire an external tool to do: typeperf "\BizTalk:Messaging(*)\ID Process" -sc 1
(but the output isn't as nice as what Andy proposes)

Scott Colestock

Friday, June 23, 2006 4:39:30 PM (Central Standard Time, UTC-06:00)

Why not just attach to all of them? No harm in that, I do it all the time.

Tom Beerley

Tuesday, June 27, 2006 7:20:28 AM (Central Standard Time, UTC-06:00)

You know, you're right - no reason not to do that that I can think of, at least in a development setting. Only downside is if you were debugging an assembly that was being used across multiple hosts and needed to break/debug in a particular context. (If you needed to attach a debugger in production or obtain a crash/hang dump, you'll want to know which host process to attach to specifically, of course.)

Scott Colestock

Comments are closed.