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 213185 - Netbeans servers manage GUI can't stop servers failed
Summary: Netbeans servers manage GUI can't stop servers failed
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 7.2
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-29 16:34 UTC by yyq2008
Modified: 2013-07-19 23:20 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description yyq2008 2012-05-29 16:34:22 UTC 
Product Version = NetBeans IDE 7.2 Beta (Build 201205031832)
Operating System = Windows 7 version 6.1 running on x86
Java; VM; Vendor = 1.7.0_03
Runtime = Java HotSpot(TM) Client VM 22.1-b02


Netbeans servers manage GUI can't stop servers failed, both tomcat 7.0.27 and glassfish 3.1.2,then I must kill server process in my taskmanager, when this done, if I changed java code or config file of my webapp, the server starts to deploy the project again automatically! it's so strange, I'm sure I killed the progress, and the server started again.
Comment 1 Vince Kraemer 2012-06-05 06:37:27 UTC 
Thanks for filing an issue.  I am not sure I can recreate the problem, based on your initial description.

Please describe how I would try to recreate the issue you are seeing, step-by-step.

Please include the text of any error messages that you might see during the process... at the step where they appeared.
Comment 2 vigor 2012-09-25 12:35:19 UTC 
Hello.
I have similar issue.

In my case this is not a netbeans issue.
My application starting separate java thread and assigning it to static variable in class.
This thread did not stoped when the context was shutting down. This situation case infinite wait procedure and Tomcat never stop.

After  killing correctly of this thread all gone fine.
Comment 3 TomasKraus 2013-07-19 23:20:16 UTC 
This does not look like GlassFish problem. Also code responsible for running glassfish was rewritten from scratch in 7.3/7.3.1 so this makes no sense now. Closing.