geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Colasurdo (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1224) shutdown.bat / shutdown.sh and associated StopServer class do not allow a hostname to be specified and is inconsistent with deploy tool
Date Wed, 23 Nov 2005 19:10:36 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1224?page=comments#action_12358403 ] 

Dave Colasurdo commented on GERONIMO-1224:
------------------------------------------

If an "are you sure" prompt is added to shutdown, then there should also be a way to suppress
the prompt (perhaps the use of the -port keyword itself).  This will be useful for user written
scripts that call to the geronimo shutdown scripts.  

> shutdown.bat / shutdown.sh and associated StopServer  class do not allow a hostname to
be specified and is inconsistent with deploy tool
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: GERONIMO-1224
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1224
>      Project: Geronimo
>         Type: Bug
>   Components: startup/shutdown
>     Versions: 1.0
>     Reporter: John Sisson
>      Fix For: 1.0

>
> The shutdown command line processing should be consistent with the deploy tool processing,
such as:
> * specifying a URI as an argument (therefore allowing connections to remote hosts)
> * using the same file that the deployer uses for storing the username and password for
the URI (see the .geronimo-deployer file used by the ServerConnection class)
> We should also consider outputting the domain and server name to the user when they request
a shutdown and prompt them to confirm that is the system they really want to shut down.  The
reason for this is the shutdown processing defaults the port to 1099 if a port isn't supplied.
 This could be dangerous in the future if a number of geronimos processes are running on a
single system because one of them ( e.g. the production system) could be using the default
port whilst the others (e.g test systems) could be using customised port numbers.  It would
be easy for a user to shut down the wrong system.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message