You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/05/14 18:37:16 UTC

[jira] Closed: (DERBY-1274) Network Server does not shutdown the databases it has booted when started and shutdown from the command line

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

Kathey Marsden closed DERBY-1274.
---------------------------------


> Network Server does not shutdown the databases it has booted when started and shutdown from the command line
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1274
>                 URL: https://issues.apache.org/jira/browse/DERBY-1274
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.1.3.1, 10.2.1.6
>            Reporter: Kathey Marsden
>         Assigned To: Fernanda Pizzorno
>             Fix For: 10.2.1.6
>
>         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.
-
You can reply to this email to add a comment to the issue online.