[
https://issues.apache.org/jira/browse/DERBY-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479536
]
John H. Embretsen commented on DERBY-2426:
------------------------------------------
Andrew commented:
> Network Server shutdown, when called from the command-line, communicates the
> shutdown command via a socket connection to the network server specified,
> which may or may not be on the local machine.
Doesn't the network server instance to be shut down have to be on the local
machine? That's how I interpret the JavaDoc for NetworkServerControl:
"With the exception of ping, these commands can only be performed from the
machine on which the server is running."
Not that this affects the validity of the argument much, I just wanted to
clarify it.
I can see arguments going both ways here. Yet I must say I too found this to be
a bit surprising (or counter-intuitive if you will) the first time I saw this
behavior. This may be mainly because of the wording of the message, since a
user may be thinking: I did not actually shut down the 10.2.1.6 server, since
it was never started, but I used it to shut down a 10.3.0.0 server...
> 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.
