You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "John Sisson (JIRA)" <de...@geronimo.apache.org> on 2005/11/23 11:27:35 UTC

[jira] Created: (GERONIMO-1224) shutdown.bat / shutdown.sh and associated StopServer class do not allow a hostname to be specified and is inconsistent with deploy tool

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
    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


[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

Posted by "Dave Colasurdo (JIRA)" <de...@geronimo.apache.org>.
    [ 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


[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

Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
     [ 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.


[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

Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
     [ 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

        

[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

Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1224?page=all ]

John Sisson updated GERONIMO-1224:
----------------------------------

    Component: startup/shutdown

> 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


[jira] Assigned: (GERONIMO-1224) shutdown.bat / shutdown.sh and associated StopServer class do not allow a hostname to be specified and is inconsistent with deploy tool

Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1224?page=all ]

Dain Sundstrom reassigned GERONIMO-1224:
----------------------------------------

    Assign To: John Sisson

> 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
>     Assignee: 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


[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

Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
    [ http://issues.apache.org/jira/browse/GERONIMO-1224?page=comments#action_12360124 ] 

John Sisson commented on GERONIMO-1224:
---------------------------------------

This is in modules\deploy-tool\src\java\org\apache\geronimo\deployment\cli\StopServer.java

> 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
>     Assignee: 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


[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

Posted by "John Sisson (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1224?page=all ]

John Sisson updated GERONIMO-1224:
----------------------------------

    Fix Version: 1.1
                     (was: 1.0)

> 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
>     Assignee: John Sisson
>      Fix For: 1.1

>
> 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


[jira] Resolved: (GERONIMO-1224) shutdown.bat / shutdown.sh and associated StopServer class do not allow a hostname to be specified and is inconsistent with deploy tool

Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Gawor resolved GERONIMO-1224.
-----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Wish List)
                   2.2
                   2.1.4
         Assignee: Jarek Gawor  (was: John Sisson)

The -hostname option was added to the shutdown command a while ago. Also, I updated the shutdown command to support saved credentials. See GERONIMO-1367 for details.


> 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: Wish
>      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.