[ http://issues.apache.org/jira/browse/GERONIMO-1224?page=all ]
Matt Hogstrom updated GERONIMO-1224:
------------------------------------
Issue Type: Wish (was: Bug)
Fix Version/s: Wish List
(was: 1.2)
Moving to wishlist.
> 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
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: startup/shutdown
> Affects Versions: 1.0
> Reporter: John Sisson
> Assigned To: John Sisson
> Fix For: Wish List
>
>
> 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
