db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (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 Sun, 16 Mar 2008 10:40:24 GMT

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

V.Narayanan commented on DERBY-3541:
------------------------------------

I get an authentication exception similar to the one above in a client/server
environment too (with the same modification to the derby codebase as above).

I however don't think I can fault derby here. 

I believe when we call quit; on ij (after booting a database in the embedded mode) 
we are trying to shutdown ij without  worrying about the database that we might 
have booted earlier. I do not think we can restrict the user from exiting (shutting 
down) the application (ij) he has started just because he has taken an authenticated 
derby connection inside the application(ij). 

This seems like a perfectly legal operation to me.

ij relying on taking a successful system shutdown derby connection (without proper
user name and password) when authentication is enabled causes the modules in the
derby system to not be shutdown in a clean fashion. 

Basically ij tries its best to do a clean shutdown of the system upon exit.

>From the analysis above I am tempted to close this JIRA issue as invalid (unless someone
has an objection).

I however think this behavior of ij when we call a quit (of not doing a clean shutdown when
authentication
is enabled) can be documented somewhere (if not already documented). If the community feels
the same
way I will raise a JIRA requesting this documentation to be included.

> 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: Security
>    Affects Versions: 10.4.0.0
>            Reporter: V.Narayanan
>         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