db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2426) java -jar derbyrun.jar server shutdown gives the wrong message
Date Thu, 08 Mar 2007 22:09:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479443

Andrew McIntyre commented on DERBY-2426:

Considering what you did here, I would say it is expected behavior.

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. The message reporting shutdown is then printed locally by the shutdown instance,
and is not a product of the server instance. 

So, the network server sends the shutdown command to the 10.3 network server, which
then happily shutsdown.  The message being reported on the shutdown side is printed by the
10.2.16 network server classes, and is reporting its version correctly, and the difference
in timestamp is due to the fact that you have messages being printed from two different jvm
instances. The message on the shutdown side is not sent from the server, but printed by the
instance that sent the shutdown command over the network after confirming shutdown close.
See NetworkServerControlImpl.shutdown().

> 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 to shut down
the server, like this:
> $ java -jar ../trunk/jars/sane/derbyrun.jar server start -noSecurityManager
> Apache Derby Network Server - alpha - (516145M) started and ready to accept
connections on port 1527 at 2007-03-08 21:48:56.308 GMT
> Apache Derby Network Server - alpha - (516145M) shutdown at 2007-03-08 21:49:18.759
> $ java -jar db-derby- server shutdown
> Apache Derby Network Server - - (452058) shutdown at 2007-03-08 21:49:19.269
> But the server I shutdown is 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.

View raw message