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 102323 - Can't profile WebApp on GlassFish if OOME detection heapdump directory has space in path
Summary: Can't profile WebApp on GlassFish if OOME detection heapdump directory has sp...
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P1 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on: 106620
Blocks:
  Show dependency tree
 
Reported: 2007-04-24 13:01 UTC by Ivan Sidorkin
Modified: 2007-09-08 10:53 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
server log (4.93 KB, text/plain)
2007-04-24 13:02 UTC, Ivan Sidorkin
Details
domain.xml with -XX:HeapDumpPath="C:\Documents and Settings\jis\My Documents\TomcatJSPExample\nbproject\private\profiler" causing the failure (19.44 KB, text/xml)
2007-04-24 14:09 UTC, Jiri Sedlacek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Sidorkin 2007-04-24 13:01:25 UTC
NetBeans IDE Dev (Build 070423)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Windows XP version 5.1 running on x86


- create Tomcate JSP Example application with space in project's path
- set Application Server as target server
- try to profile created application

server failed to start
Comment 1 Ivan Sidorkin 2007-04-24 13:02:09 UTC
Created attachment 41540 [details]
server log
Comment 2 Jiri Sedlacek 2007-04-24 13:44:49 UTC
In fact this IS somehow related to Issue 92919 - it's introduced by the OOME 
detection mechanism, but is a separate problem. This happens when OOME 
detection is enabled and heapdump target is set to a directory containing space 
in path.

As a workaround, disable OOME detection in Profiler Options or set the heapdump 
destination to a folder not containing spaces in path.

This may be a GlassFish bug with incorrectly parsed quoted JVM arguments, needs 
further investigation for 6.0.
Comment 3 Jiri Sedlacek 2007-04-24 14:09:24 UTC
Created attachment 41546 [details]
domain.xml with -XX:HeapDumpPath="C:\Documents and Settings\jis\My Documents\TomcatJSPExample\nbproject\private\profiler" causing the failure
Comment 4 Petr Jiricka 2007-04-26 18:32:44 UTC
Vince made me aware of this issue - this sounds really nasty. Changing priority
to P1 - please evaluate whether this is a J1 showstopper. Vince, what do you think?
Comment 5 Jiri Sedlacek 2007-04-26 18:57:25 UTC
P1 - Product feature does not work, no workaround exists
P2 - Product feature doesn't work, a workaround may exist but it's difficult to
use or impractical

Sorry but no word "nasty" in P1 definition. Do you have any concrete reason
which overrides the above definitions?
Comment 6 Vince Kraemer 2007-04-26 19:33:06 UTC
I think this is a p2 by the criteria.

It is going to be tricky for folks on the show floor...

If M9 is going to be 'pushed' at JavaOne those floor headaches will transfer to
a fair number of users.

Comment 7 Jiri Sedlacek 2007-04-26 19:40:28 UTC
As a workaround we could disable the OOME detection for J2EE projects for M9
until this is fixed.
Comment 8 Vince Kraemer 2007-04-26 20:02:05 UTC
That sounds like a good short-term "fix"... We still need to work through to a
real solution for the trunk.
Comment 9 Petr Jiricka 2007-04-27 08:30:43 UTC
> I think this is a p2 by the criteria.

Ok, changing to P2. (Previously this was a P3, which was not appropriate either.)
Comment 10 Jiri Sedlacek 2007-04-27 13:32:25 UTC
Implemented a workaround fixing this issue - OOME detection is disabled for all 
J2EE applications. Will file new issue for not working OOME detection.

Fixed for M10.
Comment 11 Jiri Sedlacek 2007-04-27 13:50:49 UTC
Based on discussion with the team this can be seen as a serious problem for M9 
as J1 preview release, profiling on GlassFish is broken on Windows when default 
settings are used. It would be better to have this fixed for J1.

Marking as J1_STOPPER and raising priority to P1 in order to be able to fix for 
M9.
Comment 12 Jiri Sedlacek 2007-04-27 16:41:40 UTC
Fix merged into release60_m9 branch.
Comment 13 Tomas Hurka 2007-04-27 16:43:26 UTC
Checking in profiler-cluster.zip;
/cvs/profiler/external/profiler-cluster.zip,v  <--  profiler-cluster.zip
new revision: 1.44.2.1; previous revision: 1.44
done
Comment 14 Ivan Sidorkin 2007-05-03 01:10:03 UTC
verified in 070502
Comment 15 J Bachorik 2007-06-14 10:21:41 UTC
Reopening the issue.
This is glassish or glassfish-plugin related bug. Filed an issue to glassfish plugin (the issue #106620)

Comment 16 J Bachorik 2007-06-22 12:22:32 UTC
fixed as of NB build 200706201800
Comment 17 Alexander Kouznetsov 2007-09-08 10:53:38 UTC
Verified with Beta 1