Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1F680101BF for ; Fri, 14 Jun 2013 16:50:25 +0000 (UTC) Received: (qmail 21114 invoked by uid 500); 14 Jun 2013 16:50:22 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 21058 invoked by uid 500); 14 Jun 2013 16:50:22 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 21005 invoked by uid 99); 14 Jun 2013 16:50:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jun 2013 16:50:22 +0000 Date: Fri, 14 Jun 2013 16:50:22 +0000 (UTC) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (DERBY-5652) Assert failure when bootstrapping NATIVE with invalid provider string MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas closed DERBY-5652. -------------------------------- > Assert failure when bootstrapping NATIVE with invalid provider string > --------------------------------------------------------------------- > > Key: DERBY-5652 > URL: https://issues.apache.org/jira/browse/DERBY-5652 > Project: Derby > Issue Type: Bug > Components: Services > Affects Versions: 10.9.1.0 > Reporter: Knut Anders Hatlen > Assignee: Rick Hillegas > Fix For: 10.9.1.0 > > Attachments: derby-5652-01-ac-improveErrorMessage.diff, derby-5652-01-ad-improveErrorMessage.diff, derby-5652-01-ae-improveErrorMessage.diff > > > I had accidentally put a colon at the end of the derby.authentication.provider property, and then an assert failed during authentication: > $ java -Dij.exceptionTrace=true -Dderby.authentication.provider=NATIVE:auth: -jar /code/derby/trunk/jars/sane/derbyrun.jar ij > ij version 10.9 > ij> connect 'jdbc:derby:db;create=true;user=test;password=test'; > ERROR XJ001: Java exception: 'ASSERT FAILED: org.apache.derby.shared.common.sanity.AssertFailure'. > java.sql.SQLException: Java exception: 'ASSERT FAILED: org.apache.derby.shared.common.sanity.AssertFailure'. > at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:98) > at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:142) > at org.apache.derby.impl.jdbc.Util.javaException(Util.java:299) > at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:436) > at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:353) > at org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:2360) > at org.apache.derby.impl.jdbc.EmbedConnection.(EmbedConnection.java:634) > at org.apache.derby.impl.jdbc.EmbedConnection30.(EmbedConnection30.java:73) > at org.apache.derby.impl.jdbc.EmbedConnection40.(EmbedConnection40.java:53) > at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Driver40.java:70) > at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java:255) > at org.apache.derby.jdbc.AutoloadedDriver.connect(AutoloadedDriver.java:143) > at java.sql.DriverManager.getConnection(DriverManager.java:582) > at java.sql.DriverManager.getConnection(DriverManager.java:154) > at org.apache.derby.impl.tools.ij.ij.dynamicConnection(ij.java:1528) > at org.apache.derby.impl.tools.ij.ij.ConnectStatement(ij.java:1358) > at org.apache.derby.impl.tools.ij.ij.ijStatement(ij.java:1143) > at org.apache.derby.impl.tools.ij.utilMain.runScriptGuts(utilMain.java:347) > at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:245) > at org.apache.derby.impl.tools.ij.Main.go(Main.java:229) > at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:184) > at org.apache.derby.impl.tools.ij.Main.main(Main.java:75) > at org.apache.derby.tools.ij.main(ij.java:59) > at org.apache.derby.iapi.tools.run.main(run.java:53) > Caused by: java.sql.SQLException: Java exception: 'ASSERT FAILED: org.apache.derby.shared.common.sanity.AssertFailure'. > at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:42) > at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:122) > at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:71) > ... 23 more > Caused by: org.apache.derby.shared.common.sanity.AssertFailure: ASSERT FAILED > at org.apache.derby.shared.common.sanity.SanityManager.ASSERT(SanityManager.java:98) > at org.apache.derby.impl.jdbc.Util.ASSERT(Util.java:179) > at org.apache.derby.impl.jdbc.EmbedConnection.restoreContextStack(EmbedConnection.java:2570) > at org.apache.derby.impl.jdbc.EmbedConnection.(EmbedConnection.java:636) > at org.apache.derby.impl.jdbc.EmbedConnection30.(EmbedConnection30.java:73) > at org.apache.derby.impl.jdbc.EmbedConnection40.(EmbedConnection40.java:53) > at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Driver40.java:70) > at org.apache.derby.jdbc.InternalDriver.connect(InternalDriver.java:255) > at org.apache.derby.impl.jdbc.authentication.NativeAuthenticationServiceImpl.authenticateRemotely(NativeAuthenticationServiceImpl.java:417) > at org.apache.derby.impl.jdbc.authentication.NativeAuthenticationServiceImpl.authenticateUser(NativeAuthenticationServiceImpl.java:312) > at org.apache.derby.impl.jdbc.authentication.AuthenticationServiceBase.authenticate(AuthenticationServiceBase.java:257) > at org.apache.derby.impl.jdbc.EmbedConnection.checkUserCredentials(EmbedConnection.java:1257) > at org.apache.derby.impl.jdbc.EmbedConnection.(EmbedConnection.java:404) > ... 17 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira