This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I think it would be very helpful if profiler agent would work like a service. It would listen on a port for multiple connections from profiler clients. Results would be sent to all connected clients. It would be possible to connect and disconnect to/from the running profiling agent in any time. Example: j2ee servers can run with 'silent' profiler agent for a time and when a user wants to profile server he/she only connects to the agent and start instrumentation, threads logging, heap dumping etc. After the work he/she disconnects from the agent. Agent than detects no user connected, wait for a while and switch itself to 'silent' mode (disable instrumentation and all results collecting).
This would require to implement more independent agent as it currently isn't able to cache collected profiling results. For the switching to silent mode - it would be more useful to define conditions/time periods when profiling should be done, typically the user won't be interested in immediate results without any context/history.
Maybe it would not be needed to store a history of results. A user can connect to either already profiling or silent profiler server. If a user connects to a silent server, user defines what will be profiled and starts profiling. If a user connects to already profiling server he/she can only obtain results. There should be also defined restrictions who can change profiling settings and who not.
Milestone cleanup: future->next