db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3541) quit; on ij with authentication enabled does not shutdown the derby modules that are loaded
Date Thu, 09 Jul 2009 21:08:14 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729414#action_12729414
] 

Lily Wei commented on DERBY-3541:
---------------------------------

Thank you, too. This is a good bug to look at. I mean that when authentication is enable,
quit does not do shutdown. However, I don't see how quit can shutdown when authentication
is enable. In such case, shutdown process will hit authentication failure error first before
successfully shutting down the database. I think that is the point 2 on Oystin's point if
I may quote him.

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


Mime
View raw message