geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Updated: (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 Fri, 13 Feb 2009 18:56:59 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Gawor updated GERONIMO-1224:
----------------------------------

    Issue Type: Improvement  (was: Wish)

> 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: https://issues.apache.org/jira/browse/GERONIMO-1224
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: startup/shutdown
>    Affects Versions: 1.0
>            Reporter: John Sisson
>            Assignee: Jarek Gawor
>             Fix For: 2.1.4, 2.2
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message