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 110882

Summary:	Profiler doesn't run with embedded Tomcat
Product:	profiler	Reporter:	fabriziogiudici <fabriziogiudici>
Component:	Base	Assignee:	Tomas Hurka <thurka>
Status:	RESOLVED DUPLICATE
Severity:	blocker	Keywords:	SPACE_IN_PATH
Priority:	P3
Version:	6.x
Hardware:	Macintosh
OS:	All
URL:	http://weblogs.java.net/blog/fabriziogiudici/archive/2007/07/using_the_netbe.html
Issue Type:	DEFECT	Exception Reporter:

Description fabriziogiudici 2007-07-25 09:25:32 UTC

The profiler doesn't work with the embeeded Tomcat; trying to start it in "profiling mode" gives an error message about the profiling agent not found.

I discovered that this is due to the presence of spaces in classpaths (that is, in the installation folder of NetBeans 6). My NB6 got installed in

/Users/fritz/Applications/NetBeans 6.0M10.app

(being /Applications/NetBeans 6.0M10.app the default, I just prepended my home directory). Inside the bundle there's the directory:

/Users/fritz/Applications/NetBeans 6.0M10.app/Contents/Resources/NetBeans 6.0M10

with another space between 6.0M10. Removing both of spaces (and fixing two symlinks) the profiler works fine.

I didn't test this on other o.s. yet, so at the moment I'm filing this as Mac OS X specific. BTW, Java startup scripts are usually still fragile with respect of the 
presence of spaces in the classpaths, so it could be a general idea to avoid them not only for this profiler bug, but as they could originate other problems.

Comment 1 Tomas Hurka 2007-07-25 09:46:53 UTC

Probably duplicate of issue #103047

Comment 2 fabriziogiudici 2007-07-25 09:55:24 UTC

Probably it's so. I saw 103047, but I filed a different issue since I'm working with NB6M10 (not M9) and Tomcat 6.0.13 (not 5.5.23), and the error I get is 
different. It probably depends on how it will be fixed: removing the spaces and declaring them illegal in any installation will fix both; otherwise, I think that 
these two bugs could require similar but multiple fixes in Tomcat scripts.

Comment 3 Tomas Hurka 2007-10-31 13:32:37 UTC


*** This issue has been marked as a duplicate of 103046 ***