Arun Gupta wrote:
> Why asadmin commands require the server running ?
because all the commands run on the server (at the exception of a few
local command).
why do they run on the server ? well think about jruby container which
could ship a bunch of dedicated admin commands to manage or configure
Rails applications. The client can talk to any installed server of
course and because we are so extensible the client cannot know the
capabilities on your server (did you install jruby or not, did you
install groovy or not) so the command execution request is passed to the
server where it it served.
>
> Here is the output for list-commands:
>
> -- cut here --
> ~/testbed/glassfish/v3/4_28/glassfish/bin >./asadmin list-commands
> Remote server does not listen for requests on [localhost:8080].
> Is the server up?
> Command list-commands failed.
> -- cut here --
>
> Can anybody explain why the output of list-commands (which is most
> likely the same list of commands everytime)
no that's your mistake here, depending what you have installed on the
server, you will get a different list.
> cannot be dumped w/o server running ? I'm sure there are other
> commands in that category.
>
> Also, the commands are classified as Local & Remote commands. What is
> the difference ?
>
local = executed on the client (start-domain, delete-domain and other
things that just cannot run on the server)
remote = executed on the server.
jerome
> -Arun