So you're in trouble. You've started a long running application. It's taken you half an hour to make the application reach a nice, optimized steady state. Maybe you started JRockit as a windows service. And you really didn't expect the need for having the external management agent up and running. Yet, here you are, longing to connect to the JRockit running your application using Mission Control from another machine. Perhaps to do some profiling, diagnostics or to hunt for a suspected memory leak. You start shutting down the JVM, and expect at least half an hour to pass unti... No! Wait!
Using jrcmd there is a way to bring up the agent after the fact that JRockit has been started. See one of my previous blogs for more information on how to use jrcmd.
To use jrcmd to start up the external management agent, you use the start_management_server command. Here is an example:
D:\clients\hirt>jrcmd 3848 start_management_server ssl=false authenticate=false port=4711
This command doesn't return any message upon successful completion, but on the console for process 3848 you should see:
[JRockit] Management server started on port 4711, ssl=false, authenticate=false.
