IIS 7 & IIS 8
renaming w3wp.exe processes in IIS7
Last post Apr 11, 2010 04:08 AM by CarlosAg
Apr 08, 2010 02:13 PM|LINK
Does anybody know a way to rename the w3wp.exe processes to a more user-friendly.exe name that can be mapped to the specific application pool?
For example, we have AppPool1, AppPool2, and AppPool3. Currently you see three w3wp.exe processes in the task manager when they are all running. Instead we would like to map w3wp.exe for each of these application pools to an apppool1.exe, apppool2.exe
and apppool3.exe instead so we can easily monitor and stress test the different application pools based on the process name.
I know you could do this in IIS5 using COM+ and copy/renaming/mapping the dllhost.exe - does a similar functionality exist in IIS7?
So far it looks like you can type "appcmd list wp" to get a list of wp/process mapping, however I'd like to just see the renamed w3wp.exe process dymanically appear in the task manager to avoid creating a custom wp/process mapping script each time we need
to stress test.
Any ideas would be much appreciated! Thanks.
Apr 11, 2010 01:50 AM|LINK
I do not think there is a way of doing this.
YOu can get the list of Worker processes PIDs in the worker process icon in the IIS manager for the server.
I don't understand the need to change them just for stress testing.
Simply open a site and worker process and it will stay active on that PID as per teh setting in app pool settings. If you don't close teh app pool it will always be on that PID.
Apr 11, 2010 04:08 AM|LINK
Alternatively you can easily just use Task Manager and add the Command Line column and you will see which Apppool is running in the W3WP.
- Start Task Manager
- View=>Select Columns, check Command Line and click OK.
You will see something like:
c\windows\system32\inetsrv\w3wp.exe -ap "DefaultAppPool" -v "v2.0" ...
This way you can easily map each to the AppPool.
Another way is just Launch IIS Manager and select the Server node in the Tree. Double Click "Worker Processes" and you will see all the AppPools and their PID and CPU/Memory they have. Also double clicking any of them will show you the list
of executing requests.