[
https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729625#action_12729625
]
Kathey Marsden commented on DERBY-3541:
---------------------------------------
V. Narayanan said:
>If everyone agrees we can probably document that we need to shutdown DB's
>before quitting and prevent ij from going down without closing the DB's.
I think that is just too dangerous. There are a lot of applications that use ij
scripts during their install that might hang if we do this. We do document
that exit (quit) does a shutdown.
http://db.apache.org/derby/docs/dev/tools/rtoolsijcomref33358.html
I think the best we can do is document that with authentication, shutdown
should be performed explicitly because the ij request will not succeed. I
think even adding a warning that shutdown was not successful might cause
automated scripts to fail.
> quit; on ij with authentication enabled does not shutdown the derby modules
> that are loaded
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-3541
> URL: https://issues.apache.org/jira/browse/DERBY-3541
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.4.1.3
> Reporter: V.Narayanan
> Priority: Minor
> Attachments: derby.properties, PrintStackTrace.diff,
> WithoutAuthentication_StackTrace.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
