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 Sat, 15 Mar 2008 12:54:24 GMT

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

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

We get a better picture of the above error if we replace the catch clause in

org.apache.derby.impl.tools.ij.utilMain.cleanupGo(utilMain.java:416) 

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

with a e.printStackTrace()

I get the following everytime I try to take a connection and quit ij with
authentication enabled

ij version 10.5
ij> connect 'jdbc:derby:mydb;user=oystein;password=pass';
ij> quit;
java.sql.SQLNonTransientConnectionException: Connection authentication failure occurred. 
Reason: Invalid authentication..
        at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:76)
        at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:87)
        at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:93)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:172)
        at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java:220)
        at org.apache.derby.jdbc.AutoloadedDriver.connect(AutoloadedDriver.java:119)
        at java.sql.DriverManager.getConnection(DriverManager.java:582)
        at java.sql.DriverManager.getConnection(DriverManager.java:207)
        at org.apache.derby.impl.tools.ij.utilMain.cleanupGo(utilMain.java:416)
        at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:249)
        at org.apache.derby.impl.tools.ij.Main.go(Main.java:215)
        at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:181)
        at org.apache.derby.impl.tools.ij.Main.main(Main.java:73)
        at org.apache.derby.tools.ij.main(ij.java:59)
Caused by: java.sql.SQLException: Connection authentication failure occurred.  Reason: Invalid
authentication..
        at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:45)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:119)
        at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:70)
        ... 13 more
vn@vn-laptop:~/work/workspaces/PrintStackTrace$

> 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