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 196214 - Restart of remote server just stops the server
Summary: Restart of remote server just stops the server
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 7.0
Hardware: PC Windows XP
: P4 normal (vote)
Assignee: Vince Kraemer
Depends on:
Reported: 2011-03-03 09:09 UTC by Jiri Skrivanek
Modified: 2012-11-30 12:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2011-03-03 09:09:38 UTC
If you restart server instance registered as remote domain, it just stops target server. To reproduce:

- go to Services view and add GlassFish 3.1 server instance with default values
- add another server instance with name "GlassFish Remote", select "Register Remote Domain" and type localhost host name
- start local server
- right-click "GlassFish Remote" and choose Restart
- it stops the server but doesn't start it again. The following is printed to the server log:

INFO: Server restart initiated
INFO: Stopping com.sun.enterprise.v3.server.AppServerStartup@17a6926
INFO: JMXStartupService: Stopped JMXConnectorServer: null
INFO: JMXStartupService and JMXConnectors have been shut down.
Completed shutdown of Log manager service
INFO: Shutdown procedure finished
INFO: [Thread[GlassFish Kernel Main Thread,5,main]] exiting

Product Version: NetBeans IDE Dev (Build 201103020001)
Java: 1.6.0_24; Java HotSpot(TM) Client VM 19.1-b02
System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb)
Comment 1 Vince Kraemer 2011-10-26 20:43:02 UTC
I just tested this with 7.1 dev build from 111018 and it seems like it works correctly now on a true remote server.

lowering the faux remote case to p4
Comment 2 TomasKraus 2012-11-27 15:13:55 UTC
It did server restart with NetBeans 7.3. It just took some time to refresh server status.
Comment 3 TomasKraus 2012-11-27 15:14:55 UTC
Jirko, please verify this too to make sure it really works.