[ http://issues.apache.org/jira/browse/DERBY-1274?page=comments#action_12420888 ]
Daniel John Debrunner commented on DERBY-1274: ---------------------------------------------- In many cases 'Cloudscape" should be replaced by Derby, but not in *all* cases. Thus automated blanket changes are not appropriate, each change needs to be looked at individually. Examples are when the code is referring to Cloudscape releases prior to it being open sourced as Derby. > Network Server does not shutdown the databases it has booted when started and > shutdown from the command line > ------------------------------------------------------------------------------------------------------------ > > Key: DERBY-1274 > URL: http://issues.apache.org/jira/browse/DERBY-1274 > Project: Derby > Type: Bug > Components: Network Server > Versions: 10.2.0.0, 10.1.2.3 > Reporter: Kathey Marsden > Assignee: Fernanda Pizzorno > Attachments: derby-1274.diff, derby-1274.stat, derby-1274v2.diff, > derby-1274v3.diff, derby-1274v3.stat, derby-1274v4.diff, derby-1274v4.stat > > If network server is started and shutdown from the comand line t does not > shutdown the database. This can is evidenced by the fact that the db.lck > file remains after the following steps. > java org.apache.derby.drda.NetworkServerControl start & > <some database access> > java org.apache.derby.drda.NetworkServerControl shutdown > There is much discussion about the correct behavior of NetworkServer in this > regard related to embedded server scenarios in DERBY-51, but it seems clear > in this case the databases should be shutdown. > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
