Multiple iwperl.exe spawned

Hazzie

Hi,

Occasionaly one of our workflows spawns many iwperl.exe process's that just dont seem to end and consume lots of processor time. iwstat reports 3000-4000 operations a second. When end task at random an iwperl from the task list this causes a lot of other iwperl.exe's to finish and the operations per second drops to about 12.

The problem i have at the moment is that i cannot find a way to relate which iwperl.exe in the task list relates to which script called it. Is it possible to find what called an iwperl process once its in the Task List?

The only way i can see about doing it at the moment is to make multiple copies of the iwperl.exe and rename them iwperl1.exe iwperl2.exe etc and the go through the workflow and change all the script calls to these new iwperl.exe's. This will mean that we will be able to see different iwperls in the task list and i will be able to marry up which script called it and narrow my problem down a bit.

I am just hoping there is a more elegant way to do this.

Thoughts?

Hazzie
TS 5.5.2 on NT.

Adam Stoller

What SP level are you on with 5.5.2?

I believe someone recently posted a pointer to a windows process tree viewer (don't remember which one) - but you might be able to use something like that to track down where the iwperl processes were spawned from.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com