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 141163

Summary:	GlassfishV3 can not start in profile mode
Product:	serverplugins	Reporter:	Rashid Urusov <rashid>
Component:	GlassFish	Assignee:	_ pcw <pcw>
Status:	VERIFIED FIXED
Severity:	blocker
Priority:	P4
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:

Description Rashid Urusov 2008-07-22 14:05:56 UTC

I tried to profile empty web application using GlassfishV3
but server didn,t start.
With Glassfish V2 there was no problem.

Output.log  :
profile-j2ee:
start-profiled-server-extraargs:
Server GlassFish V3 is stopping
stop-domain running on GlassFish V3
Server GlassFish V3 is stopping
GlassFish V3 Stop Failed
C:\temp\WebApplication4\nbproject\profiler-build-impl.xml:19: The following error occurred while executing this line:
C:\temp\WebApplication4\nbproject\profiler-build-impl.xml:30: Starting server in profile mode failed.
BUILD FAILED (total time: 10 seconds)

Comment 1 _ pcw 2008-07-22 19:22:24 UTC

Profiling is not supported on V3 right now.  Maybe NB 7.0.

There may be a bug to fix here since I don't think you should have been allowed to start it in the first place.

Not a P2 though, lowering to P3.

Comment 2 _ pcw 2008-07-27 05:55:22 UTC

I get this result when I try to run the profiler against a running V3 instance:

profile-j2ee:
start-profiled-server-extraargs:
Server GlassFish V3 15A Patch is stopping
stop-domain running on GlassFish V3 15A Patch
Server GlassFish V3 15A Patch is stopping
GlassFish V3 15A Patch was stopped.
C:\tmp\WebApplication5\nbproject\profiler-build-impl.xml:19: The following error occurred while executing this line:
C:\tmp\WebApplication5\nbproject\profiler-build-impl.xml:30: java.lang.UnsupportedOperationException: Starting in
profile mode is not supported by this server.
BUILD FAILED (total time: 2 seconds)

Due to how the profiler action is implemented now, showing the exception as above (which does have a clear message -
"Profile mode not supported by this server") is the best we can do for 6.5 at this time.

It looks like what happened in your case is that the server failed to stop, so it never got to the unsupported message.
 Do you know why the server would have failed to stop?  Were you previously debugging and stopped at a breakpoint perhaps?

Lowering to P4 priority.  May close as invalid, depending on response.

Comment 3 _ pcw 2008-08-23 01:32:27 UTC

You're in luck - we implemented profiling support for V3. Yay!

Closing as fixed.

Comment 4 Rashid Urusov 2008-08-27 11:09:34 UTC

verified in Build 200808250201