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 76858 - Tomcat is sometimes not finished after Stop profiling
Summary: Tomcat is sometimes not finished after Stop profiling
Status: VERIFIED DUPLICATE of bug 69951
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2006-05-25 14:03 UTC by ehucka
Modified: 2006-09-14 11:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ide log (4.04 KB, text/plain)
2006-05-25 14:05 UTC, ehucka 		Details
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-05-25 14:03:15 UTC 
profiler 5.5 060525

Sometimes after invoking of Stop profiling action and ReRun Last profiling
action a web application is not started again. There is some exceptions thrown,
Tomcat looks like it is running and Processes in Runtime tab contains the
profiled application node. After finishing of IDE there is remaining profiling
process which must be killed to release profiling port.
Comment 1 ehucka 2006-05-25 14:05:00 UTC 
Created attachment 30599 [details]
ide log
Comment 2 Jiri Sedlacek 2006-05-25 14:09:56 UTC 
Seems much more like a duplicate of Issue 69951 than a Tomcat problem. There 
are no Tomcat-related messages in the log. Please mark as duplicate of that 
issue if you agree.
Comment 3 ehucka 2006-05-25 14:21:27 UTC 
Seems it is the same. 
Strange, why the Processes node contains 'MyApplication (profile-j2ee)' node?
I found out it occures more frequently when the profiler is profiling for a
'long' time on background (~ 10 minutes without a user action).

*** This issue has been marked as a duplicate of 69951 ***
Comment 4 Jiri Sedlacek 2006-05-25 14:26:52 UTC 
Because of the exception the Profiler terminates connection to agent, thus the 
agent doesn't obtain a request from the Profiler to stop Tomcat's VM and the 
webapp keeps running => can still be seen in Processes tab whereas profiling 
session has already finished.
Comment 5 ehucka 2006-05-25 14:49:23 UTC 
But during normal profiling the Processes node doesn't contain any process.
Comment 6 ehucka 2006-09-14 11:02:02 UTC 
verified