OK, this is as designed. When you run in 'controlled' mode, the JVM is
preempted at startup until the UI attaches to the process and starts
profiling. This mode is primarly provided so you can trace an entire
application from the very beginning when running Java applications from
scripts. The idea is you have a complex environment such as a server
that
you need to profile startup of. Starting the server is far to
complicated
to do from the UI directly so you simply modify the batch file that
starts
your application and you are good to go.
If you wish for the application not to be preempted and you only wish to
profile at some point in the future then you will want to use 'enabled'
mode.
Hope this helps.
"Martin" <martin@xxxxxxxxxxxxxx> wrote in message
news:opsbf832iilm6d52@xxxxxxx
I'm a little further on now. In serviceconfig.xml I changed the
RASERVER_HOME variable from "F:\hyades" which is a mapped drive, to
"C:\Program Files\hyades" and restarted the data collection service. I
no
longer get an error message when I use "server=controlled", it just
hangs
- and I still get stack traces and error messages with the other
options.
On Tue, 20 Jul 2004 01:38:33 +0100, Martin <martin@xxxxxxxxxxxxxx>
wrote:
>
> I get this error when I try to run the profiler:
>
> Error occurred during initialization of VM
> Could not find -Xrun library: piAgent.dll
>
> piAgent.dll is on my PATH and my RASERVER_HOME is set correctly and I
> pass "-XrunpiAgent:server=application" to the VM - any ideas? This on
> the latest build with Eclipse 3.0.
>
> Thanks,
> Martin