geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Jiang (JIRA)" <j...@apache.org>
Subject [jira] Created: (GSHELL-162) "geronimo/stop-server -p 3099" can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties.
Date Fri, 27 Feb 2009 04:50:01 GMT
"geronimo/stop-server -p 3099" can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties.
--------------------------------------------------------------------------------------------------------------------------

                 Key: GSHELL-162
                 URL: https://issues.apache.org/jira/browse/GSHELL-162
             Project: GShell
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: CLI
         Environment: XP + SUN JDK 1.5 + geronimo-tomcat-2.1.4-snapshot_20090225
            Reporter: Shawn Jiang
            Assignee: Jason Dillon


Reproduce steps:
1, Change NamingPort=3099  in var/config-substitutions.properties.

2, Use GShell command "geronimo/start-server" to start the server. 

3, Use Use GShell command "geronimo/stop-server -p 3099" to stop the server.

Expected result: the server could be shutdown and return to the GShell command line mode.
Actually result: The server can't be shutdown, can't return to the GShell command line.


Root Cause:

You have to use "geronimo/start-server -p 3099" to start server if you want use "geronimo/stop-server
-p 3099"  to stop the server.

I believe there should not be a -p args for geronimo/start-server command.  Instead, geronimo/start-server
should read NamingPort=3099 in config.substitutions.properties to avoid the problem.



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