OsoftPackageLauncher.exe - what is this?

Question

The osoftPackageLauncher.exe process was running at 80-99% CPU on the app server during eData package executions. What is this process, and how should it behave?
BPC 7MS SP6

Answer 1

Thank you, Sorin. I think I get it now. I can either deal with an EXE process that consumes up to 99% of CPU during package run, or deal with a possible memory leak in COM+ service (due to MS bug). I think during a long package run that 99% cpu utilization on the app server will cause connection issues for users. So, might be better to utilize the COM+ (and set it to recycle at 900,000).
Either way, I hope there's a more solid resolution very soon. Thanks again, Sorin.
For future reference, here's the detail of the note your referenced:
Summary
Symptom
The DM Server COM+ application memory is not released after package execution.
Other terms
Planning and Consolidation 75M SP1 Microsoft, DM "Memory leak", IM 2174817 2009
Reason and Prerequisites
With End of package execution, SSIS class library is not released from
memory. (MS Bug)
Solution
Corrected in 75M SP1.
Using Exe file type wrapper for running out of process from COM+.
[Additional Change]
Name:RUNPKGBYEXE
Description:  AppSet Parameter for executing package out of process from COM+
Valid value:
    0 = Run in process (current behavior)
    1 = Run out of process
Default value: 1
So if you want to use current behavior, the parameter's value must be set to 0.