Sorry to be dense / have not been following along closely enough lately...
But —nosync will be supported as an option on start-instance in 3.1?
If so, that’s probably good enough... Would be nice to have on restart-instance as well but (while I’ll have to double check with our operations team) I believe our automated deployment scripts are all calling stop-instance and then start-instance
On 7/20/10 10:23 PM, "Paul M Davies (Oracle)" <paul.m.davies_at_oracle.com> wrote:
Hi,
I know that in the meeting we decided not to include --nosync and --fullsync (not syncfull as you have) in restart-instance, instead relying on the settings of these options in the start-instance command that initially started the instance. Should we reconsider this decision in the light of Sean's request that restart-instance accept an optional flag to not attempt to sync with the DAS?
Regards,
-Paul
On 07/20/10 19:12, Jennifer Chou wrote:
I updated the cluster design spec Cluster Admin Commands usage from the admin iteam discussion. There are a few open issues, and some attributes not yet implemented, but it should be close to what the final usage should be
http://wikis.sun.com/display/GlassFish/V3.1Clustering
On 7/21/2010 2:57 AM, Paul M Davies (Oracle) wrote:
Hi Ken,
--help displays the man page, which has not been written yet - hence the empty template, which is static text.
To get the usage message, try typing the command with an option that you know to be invalid (--usage, for example).
Regards.
-Paul
On 07/20/10 18:52, Ken Paulsen wrote:
My build from the end of last week:
glassfish/bin> ./asadmin delete-instance --help
NAME :
delete-instance -
SYNOPSIS :
delete-instance [--nodeagent=nodeagent] instance_name
OPTIONS :
--nodeagent
OPERANDS :
instance_name -
Command delete-instance executed successfully.
My build from today:
glassfish/bin> ./asadmin delete-instance --help
NAME :
delete-instance -
SYNOPSIS :
delete-instance instance_name
OPTIONS :
OPERANDS :
instance_name -
Command delete-instance executed successfully.
Looks like someone's checkin broke the Admin Console....
Ken
On 07/20/2010 06:42 PM, Anissa Lam wrote:
Hi,
Is the CLI to delete-instance recently changed ? GUI was working on deleting an instance on Sunday, but it is failing now.
Is this changed recently ?
Usage: asadmin [asadmin-utility-options] delete-instance
[-?|--help[=<help(default:false)>]] instance_name
We no longer need to pass in node ?
[#|2010-07-20T18:36:01.685-0700|SEVERE|glassfish3.1|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin|_ThreadID=81;_ThreadName=http-thread-pool-4848(2);| Invalid option: nodeagent|#]
[#|2010-07-20T18:36:01.706-0700|SEVERE|glassfish3.1|com.sun.jersey.spi.container.ContainerResponse|_ThreadID=81;_ThreadName=http-thread-pool-4848(2);|The RuntimeException could not be mapped to a response, re-throwing to the HTTP container
org.glassfish.admin.rest.CliFailureException: Invalid option: nodeagent
at org.glassfish.admin.rest.resources.TemplateExecCommand.executeCommand(TemplateExecCommand.java:124)
at org.glassfish.admin.rest.resources.TemplateCommandDeleteResource.processDelete(TemplateCommandDeleteResource.java:94)
at org.glassfish.admin.rest.resources.TemplateCommandDeleteResource.hack(TemplateCommandDeleteResource.java:137)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
thanks
Anissa.
---------------------------------------------------------------------
To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
--
Sean Comerford, Software Engineer
ESPN.com Site Architecture Group
Office: 860.766.6454 Cell: 860.329.5842