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 101376

Summary:	[J2EE] Incorrect results when modifying profiling with root methods selected
Product:	profiler	Reporter:	J Bachorik <yardus>
Component:	Base	Assignee:	Tomas Hurka <thurka>
Status:	NEW ---
Severity:	blocker	CC:	gsporar
Priority:	P3
Version:	5.x
Hardware:	All
OS:	Linux
Issue Type:	DEFECT	Exception Reporter:

Description J Bachorik 2007-04-17 14:46:05 UTC

NetBeans IDE Dev (Build 200704151800)
Linux version 2.6.17-11-generic running on i386
Java HotSpot(TM) Server VM 1.6.0-b105
Bundled Tomcat

Steps to reproduce:
1. Start the TomcatJSPExample application
2. Click "Panel Tag File" "Execute" link
3. Take snapshot
4. Expand the callgraph to the lowest level
5. Select "org.apache.jsp.jsp2.tagfiles.panel_jsp._jspService as a root method
6. Modify profiling
7. Repeat steps 2-4 and notice that those callgraphs are different; the latter
one seems to be trimmed down somehow - it doesn't display the lowest call graph
levels

Comment 1 J Bachorik 2007-08-22 10:09:00 UTC

this functionality is "as-designed". lazy instrumentation combined with instrumentation filters can cause random
skipping of some parts of the profiled application. as this skipping doesn't involve parts particularly interesting to
the user (eg. root methods) i'm lowering the priority to P3