[
https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579040#action_12579040 ]
V.Narayanan commented on DERBY-3541:
------------------------------------
Upon calling quit in ij, ij tries to shutdown the connection. The code relevant to this
is found here
org.apache.derby.impl.tools.ij.utilMain.cleanupGo(utilMain.java:416)
here we do the following
if (d!=null) { // do we have a driver running? shutdown on exit.
try {
DriverManager.getConnection("jdbc:derby:;shutdown=true");
} catch (SQLException e) {
// ignore the errors, they are expected.
}
}
now with authentication enabled trying to take a connection to shutdown like done in
the above code will result in an exception
ij> connect 'jdbc:derby:;shutdown=true';
ERROR 08004: Connection authentication failure occurred. Reason: Invalid authentication..
This is the reason why upon a quit; in ij with authentication enabled and in the
embedded mode the modules are never shutdown.
> 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.