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.
Profiler 070119 NetBeans IDE Dev (Build 200701141900) 1.5.0_10; Java HotSpot(TM) Client VM 1.5.0_10-b03 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251 Sun Java System Application Server Enterprise Edition 9.1 (build b28) Steps to reproduce: - Try to Profiler Enterprise Application targeting GlassFish - RESULT: Server fails to start due to incorrect jvm-arguments. See attached log and domain.xml files. After removing quotes from jvm-argument I was able to start server in profiling mode manually and attach Profiler. com.sun.enterprise.server.PELaunch start java.lang.NoClassDefFoundError: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\Work\Temp\NBProjects\OrderSystem\nbproject\private\profiler -agentpath:C:\Program Files\NetBeans 6/0 Dev\profiler1\lib\deployed\jdk15\windows\profilerinterface/dll="C:\Program Files\NetBeans 6/0 Dev\profiler1\lib",5140 Exception in thread "main"
Created attachment 37551 [details] Configuration file after Profile Project action
Created attachment 37552 [details] Server log
*** Issue 77638 has been marked as a duplicate of this issue. ***
Seems like a general space-in-path problem, isn't related just to GlassFish or profiling J2EE applications. As a workaround until fixed NetBeans have to be installed on path without spaces.
There is an easy fix for Windows - to remove quotes from path like this: -agentpath:C:\Program Files\NetBeans 6/0 Dev\profiler1\lib\deployed\jdk15\windows\profilerinterface/dll=C:\Program Files\NetBeans 6/0 Dev\profiler1\lib,5140 This is really annoying issue. Would you like to recommend user to reinstall IDE from its default path if this feature is required? I believe the priority could be raised since this is the main button "Profile Project" which doesn't work for GlassFish on the main platform.
REGRESSION since Profiler 5.5.1
Note that just removing the quotes isn't a fix, it's just a workaround which luckily works - or do you really think that "NetBeans 6/0 Dev" looks like correct path for "NetBeans 6.0 Dev"? The Profiler thinks that the argument is a classname, not agent binaries folder (translating 6.0 to 6/0).
Why not? I would like to mention also "profilerinterface/dll" in this argument.
... which is also incorrect - in fact the whole contents in quotes is interpreted incorrectly. The problem is caused by an OutOfMemory detection mechanism implemented in 6.0. As a workaround, disable it by selecting Do nothing in On OutOfMemoryError: section of Profiler Options. Note that this bug will be fixed on a more general level covering all SPACE_IN_PATH related problems. Lowering priority - simple workaround exists.
Moreover the profiled project should be created on path without spaces.
In fact space in project's path shouldn't be a problem. SPACE_IN_PATH problems are caused by space in profiler1 cluster's path.
Space in project's path definitely shouldn't be a problem as well as space in NB path. But it is. I created two projects. One with spase in path, other without. I can profile application that doesn't have space in path and can't another one.
If so then please file a separate issue, this doesn't seem to be related to this problem - at least it's most likely not caused by the OOME detection mechanism.
Fixed for M9.
Verification is blocked by issue 102467
Verified with Profiler 070426 NetBeans IDE 6.0 Preview (M9, build 070427) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251 There is also another similar issue 102323 which is not fixed yet. Disabled OOME mechanism to verify the issue.