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 52377 - improve JVM properties editing experience
Summary: improve JVM properties editing experience
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 4.x
Hardware: PC All
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-14 12:13 UTC by L Martinek
Modified: 2012-09-03 14:16 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description L Martinek 2004-12-14 12:13:41 UTC
[NetBeans 4.0 FCS, JDK 1.4.2_06]

When I want to change server some properties, I
have to do it when server is running, otherwise
JVMs node are not accessible. But when I change
it, server is not automatically restarted and is
running with old properties. It should be possible
to change properties even with not running server.

Imaging following scenario:
1. Appserver is not running and you want change
debug port. JVMs node is not available, so you
have to start appserver.
2. Change debug port in properties.
3. Stop server.
4. Start server.
You have to do it in 4 steps!
Comment 1 _ ludo 2004-12-14 15:52:24 UTC
cannot agree more... But this is a constraint from the app server
admin area, not the plugin: to administer the server, icnlduing
changinf debug port, the admin server (which is for PE the same as the
isntance VM) has to be up and running.
For EE enterprise edition, the 2 processes are separate...

Move to RFE.
Comment 2 Vince Kraemer 2005-08-26 23:12:04 UTC
started e-mail thread on dev@glassfish.dev.java.net.
Comment 3 Vince Kraemer 2008-04-26 22:08:43 UTC
We need to find a public way to change the properties of a local server without starting that server... and then having
to restart the server to have them take effect.  This should be addressed in the v3 plugin... in either 6.5 and/or 7.

If the changes can get into the v2 plugin... without a lot of extra work... all the better.
Comment 4 Vince Kraemer 2009-12-10 12:54:57 UTC
no bug should be assigned to issues. distributing the load.
Comment 5 Vince Kraemer 2010-02-04 12:21:04 UTC
shift to me.
Comment 6 TomasKraus 2012-09-03 14:16:27 UTC
It is possible to implement offline JVM options editing for local domain but it won't be easy.
There is API in GF that allows to read, modify and store domain.xml file. But it means that GlassFish plugin would have to load some classes from modules and use them to display and modify domain.xml content (servers, configs and jvm-options).

There is no chance to make such a changes in 7.3.