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 119841

Summary: java.net.SocketException: Connection reset when trying to profile ent. app. on GF
Product: profiler Reporter: _ gsporar <gsporar>
Component: BaseAssignee: issues@profiler <issues>
Status: RESOLVED WONTFIX    
Severity: blocker    
Priority: P3    
Version: 6.x   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Exception Reporter:
Attachments: IDE log file
GlassFish server log
JVM crashlog

Description _ gsporar 2007-10-23 23:47:11 UTC
Using NB 6 Beta2 on JDK6u1 on WindowsXP.  I installed the "All" download and had the installer put GlassFish build 58 on
my system.

Here is what I did:

1. Create the "Servlet Stateless" sample Enterprise Application (it is under Samples > Enterprise in the new project
dialog).

2. Run the Servlet Stateless application.  Everything works fine: GlassFish starts, the app. gets deployed, the web
browser gets started, the page gets displayed, etc.

3. Back in the IDE, right-click the enterprise application (ServletStatless) and choose Profile.

4. Do CPU profiling, select the sayHello method in the stateless session bean as a root method.  Set the Filter to "All
classes."

5. Click the Run button in the profiler dialog box.

It appears that GlassFish gets shutdown correctly, and then is restarted (which is what I would expect).  But something
goes wrong during the restart.  This message is in the IDE log file:

java.net.SocketException: Connection reset

And over on the Services tab the GlassFish entry has that funny-looking icon that includes what appears to be a "pause"
button from a VCR....

I will attach both log files.
Comment 1 _ gsporar 2007-10-23 23:48:18 UTC
Created attachment 51531 [details]
IDE log file
Comment 2 _ gsporar 2007-10-23 23:50:32 UTC
Created attachment 51532 [details]
GlassFish server log
Comment 3 Jiri Sedlacek 2007-10-24 15:11:25 UTC
Reproduced. As a workaround before fixed please use JDK5, this works fine for me.
Comment 4 Jiri Sedlacek 2007-10-24 16:23:43 UTC
Created attachment 51596 [details]
JVM crashlog
Comment 5 Jiri Sedlacek 2007-10-24 16:25:36 UTC
Can by reproduced by directly profiling the project without restarting the server. Seems to only happen for Part of
Application, Entire Application works fine. Caused by profiled JVM crash, see the above crashlog.
Comment 6 Tomas Hurka 2007-11-07 10:37:18 UTC
Changing target milestone to dev, since NetBeans 6.0 is in high resistance mode.
Comment 7 J Bachorik 2008-03-29 11:37:06 UTC
changing milestone
Comment 8 Tomas Hurka 2011-02-03 11:01:25 UTC
This is JDK bug. Closing as wontfix.