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.

Bug 74085 - Profiling of an Web application cannot be started after previous profiling problem
Summary: Profiling of an Web application cannot be started after previous profiling pr...
Status: VERIFIED DUPLICATE of bug 82722
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-28 13:02 UTC by ehucka
Modified: 2006-10-23 15:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ehucka 2006-03-28 13:02:21 UTC 
I found out start of profiling of an web application after restart of IDE
enforced by e.g. profiler deadlock or some problem with profiling, always ends
by error:

WebApplication/nbproject/profiler-build-impl.xml:30: Starting server in profile
mode failed.

It can be fixed by restart IDE and start tomcat in profile mode.
Comment 1 Jiri Sedlacek 2006-06-08 11:41:20 UTC 
May be the similar problem as seen when profiling GlassFish. After any error 
occurs during server startup/profiling and profiling session and/or server are 
killed, agent identification file in user directory ($HOME/.nbprofiler) isn't 
deleted. This causes problems when starting another profiling session 
(STATE_INACTIVE instead of STATE_STARTING).
Comment 2 Tomas Hurka 2006-08-18 12:52:38 UTC 
This issue was hopefully fixed together with issue #82722. Please reopen if you can still reproduce it.

*** This issue has been marked as a duplicate of 82722 ***
Comment 3 ehucka 2006-09-14 10:52:29 UTC 
verified