profiler 061019

Automated tests of CPU profiling fail by 'test not finished'. It seems the
jfluid doesn't respond for a long time so xtest killed it with threaddump.
The automated test case use a main class with thousand methods calling each other.
It can be reproduced manually by j2se-simple project from
jfluid/test/functional/data/projects, main class  simple.cpu.Methods2, entire
application. Sometimes it ends with:
*** Profiler warning (Thu Oct 19 11:03:40 CEST 2006): timed out while trying to
connect to the target JVM.
*** Profiler error (Thu Oct 19 11:03:40 CEST 2006): connection with server not open
IDEAppStatusHandler - error: Failed to establish socket connection with the
target JVM.

Threaddump dumped by xtest contains strange number of JFluid Separate Command
Execution Thread.