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.
| Summary: | Server status is not refreshed after Stop Profile action | ||
|---|---|---|---|
| Product: | profiler | Reporter: | Alexander Kouznetsov <mrkam> |
| Component: | Base | Assignee: | issues@profiler <issues> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 95234, 110496, 182772 | ||
| Bug Blocks: | |||
|
Description
Alexander Kouznetsov
2007-01-17 15:53:51 UTC
This is caused by the fact that the server isn't correctly stopped by stopping the profiling session, System.exit() is called instead. This will be fixed once new stopServer() method will be added to serverplugin profiling API which can be used by the Profiler instead of killing the server. The same behavior is experienced if the Profiler is detached from Web Application on Tomcat and user selected to terminate the application upon detaching. Is there any issue about stopServer() method in serverplugin profiling API to add the dependency? AFAIK not, you may file such issue in serverplugins module. At this time we need these calls: - stopServer() - to fix this issue - refreshServer() - to fix Issue 92714 but this is quite important part and needs more precise analysis at the Profiler side - definitely not for 6.0. Is there any progress in this area? Could you please file these issues if they've not been already filed since you the best person to do this as well as to verify the fix. Filed an issue 110496 to serverplugins *** Issue 145563 has been marked as a duplicate of this issue. *** Issue #110496 must be resolved first NetBeans.org Migration: changing resolution from LATER to WONTFIX |