[
https://issues.apache.org/jira/browse/DERBY-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479538
]
Andrew McIntyre commented on DERBY-2426:
----------------------------------------
> Doesn't the network server instance to be shut down have to be on the local
> machine?
It looks like the setupSocket method used by NetworkServerControlImpl will use
whatever hostname / portNumber was passed in on the command line. So, if
invoked from the command line, this is to be expected from the code, if not
necessarily intuitive.
Plus, the command line help for the shutdown command states:
shutdown [-h <host>][-p <portnumber>] [-ssl <sslmode>]
I guess the real question is "can a server of a lower version be allowed to
shutdown a server of higher version without authentication or authorization"?
For that question, I have no immediate answer.
> java -jar derbyrun.jar server shutdown gives the wrong message
> --------------------------------------------------------------
>
> Key: DERBY-2426
> URL: https://issues.apache.org/jira/browse/DERBY-2426
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Reporter: Bernt M. Johnsen
> Priority: Trivial
>
> If e.g. I have a 10.3 server running and uses derbyrun.jar from 10.2.1.6 to
> shut down the server, like this:
> $ java -jar ../trunk/jars/sane/derbyrun.jar server start -noSecurityManager
> Apache Derby Network Server - 10.3.0.0 alpha - (516145M) started and ready to
> accept connections on port 1527 at 2007-03-08 21:48:56.308 GMT
> Apache Derby Network Server - 10.3.0.0 alpha - (516145M) shutdown at
> 2007-03-08 21:49:18.759 GMT
> $ java -jar db-derby-10.2.1.6-bin/lib/derbyrun.jar server shutdown
> Apache Derby Network Server - 10.2.1.6 - (452058) shutdown at 2007-03-08
> 21:49:19.269 GMT
> But the server I shutdown is 10.3.0.0 alpha! Also the client reports a
> different timestamp than the server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
