db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2426) java -jar derbyrun.jar server shutdown gives the wrong message
Date Mon, 06 Jul 2009 19:25:14 GMT

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

Rick Hillegas updated DERBY-2426:
---------------------------------

    Issue & fix info: [Repro attached]
             Urgency: Normal

Triaged for 10.5.2: assigned normal urgency and noted that a repro is attached.

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


Mime
View raw message