[ http://issues.apache.org/jira/browse/DERBY-1274?page=all ]
Fernanda Pizzorno updated DERBY-1274:
-------------------------------------
Attachment: derby-1274v3.diff
derby-1274v3.stat
The attached patch (derby-1274v3.diff) is v2 + a test (as suggested by Bryan
Pendleton).
The network server will be started from the command line before the test
starts, the test will create a database, create a table, insert some data and
then shut down the server and check that the file db.lck does not exist. Then
it will start the server from the api, create the database ... etc, shut down
the server and check that the file db.lck exists.
I think the test would look better if the server had been started from the
command line inside the test. Does anyone have a suggestion on how to do that?
I have successfully run derbyall with this patch. Can someone please review it?
> 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
>
> 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
