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 77592 - Profiling hangs Tomcat 5.5 when using XSLT Transformer
Summary: Profiling hangs Tomcat 5.5 when using XSLT Transformer
Status: CLOSED DUPLICATE of bug 84002
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
: 76506 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-06-08 20:22 UTC by hal200
Modified: 2007-03-14 11:24 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
As requested :) (98.26 KB, text/plain)
2006-06-27 15:22 UTC, hal200 		Details
MESSAGES.LOG from profiler Q-Build 200606151230 (32.94 KB, text/plain)
2006-07-04 20:05 UTC, hal200 		Details
Tomcat Log files (1.52 KB, application/x-compressed)
2006-07-04 20:06 UTC, hal200 		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 hal200 2006-06-08 20:22:29 UTC 
Using Java 1.5.0_05, Tomcat 5.5.15, Netbeans 5.0 or 5.5 beta.

When profiling the following code, 

				javax.xml.transform.TransformerFactory factory =
TransformerFactory.newInstance();
				log.debug("loading stylesheet " + url.toExternalForm());
				is = url.openStream();
				Source xslSource = new StreamSource(is);
				xslSource.setSystemId(url.toExternalForm());
				translet = factory.newTemplates(xslSource);
				templates.put(url.toExternalForm(), translet);

I get the following errors on the attached server console, at which point the
server hangs.

DEBUG [15:19:37] - loading stylesheet file:///D:/config/transform/internal/probl
em-map.xsl
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
Profiler Agent Warning: JVMTI classLoadHook: class name is null.
Profiler Agent Warning: Failed to lookup cached class problem_map

Any help would be greatly appreciated.
Comment 1 J Bachorik 2006-06-27 14:52:35 UTC 
I used your code fragment to create a small test class but I wasn't able to
reproduce the problem.
Could you send us your MESSAGES.LOG file?
Comment 2 hal200 2006-06-27 15:22:16 UTC 
Created attachment 31420 [details]
As requested :)
Comment 3 J Bachorik 2006-06-28 10:02:10 UTC 
Still no luck in reproducing the bug. Do you, by any chance, use any kind of
bytecode modifying framework (like AOP, ORM etc.)? 
Also, the "problem_map" class is a normal class or something generated by a
framework from the XSL file?
Could you, plz, send us the corresponding tomcat logs? For a time being you
could give a try to the latest NB5.5 + Profiler 5.5 q-builds; there was an issue
with classloaders fixed - might help.
Comment 4 Tomas Hurka 2006-06-28 10:13:58 UTC 
*** Issue 76506 has been marked as a duplicate of this issue. ***
Comment 5 hal200 2006-07-04 20:05:37 UTC 
Created attachment 31635 [details]
MESSAGES.LOG from profiler Q-Build 200606151230
Comment 6 hal200 2006-07-04 20:06:33 UTC 
Created attachment 31636 [details]
Tomcat Log files
Comment 7 hal200 2006-07-04 20:08:26 UTC 
As requested, I have tested this with the latest q-build and it still fails for
me.  I have also included the Tomcat logs, but they don't appear to be terribly
informative.  

Would it be possible for you to attach the code you have been using to reproduce
the issue so I can test it locally?
Comment 8 Tomas Hurka 2006-09-01 20:03:13 UTC 
This issue is duplicate of #84002
Comment 9 Tomas Hurka 2006-09-01 20:03:30 UTC 

*** This issue has been marked as a duplicate of 84002 ***
Comment 10 Alexander Kouznetsov 2007-03-14 11:24:47 UTC 
Closing old issues