Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 29039 invoked from network); 13 Apr 2006 20:04:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Apr 2006 20:04:58 -0000 Received: (qmail 66866 invoked by uid 500); 13 Apr 2006 20:04:56 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 66797 invoked by uid 500); 13 Apr 2006 20:04:55 -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 66728 invoked by uid 99); 13 Apr 2006 20:04:55 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Apr 2006 13:04:55 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Apr 2006 13:04:54 -0700 Received: from brutus (localhost.localdomain [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CE448714294 for ; Thu, 13 Apr 2006 20:04:03 +0000 (GMT) Message-ID: <71697527.1144958643842.JavaMail.jira@brutus> Date: Thu, 13 Apr 2006 20:04:03 +0000 (GMT+00:00) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Resolved: (DERBY-1173) conglomerate (129) requested does not exist error on create table after aborting and rerunning jdbcapi/checkDataSource test with client. In-Reply-To: <272290211.1143834392267.JavaMail.jira@ajax> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-1173?page=all ] Kathey Marsden resolved DERBY-1173: ----------------------------------- Resolution: Invalid Seems clear that this issue is related to the partial cleanup of the database directory by the test harness and not a product issue. Currently the long pause/hang does not seem to be occurring, so can't verify for sure. I will run more tests and then hopefully be able to reenable the checkDataSource test. > conglomerate (129) requested does not exist error on create table after aborting and rerunning jdbcapi/checkDataSource test with client. > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1173 > URL: http://issues.apache.org/jira/browse/DERBY-1173 > Project: Derby > Type: Bug > Components: Network Client > Versions: 10.0.2.1 > Reporter: Kathey Marsden > Priority: Minor > Fix For: 10.2.0.0 > Attachments: first_run_testfiles_afterhang.zip, rerun_test_files_with_corrupt_db.zip, traces_on_hang.txt > > I am changing the description of this bug because I have a clearer reproducible case for it and the old description has some information that is probably not relevant. > If jdbcapi/checkDataSource30.java is aborted at a certain point in the test and then rerun with the server still running, it will give a conglomerate not found error and the database will be corrupted. > To Reproduce: > 1) Enable checkDataSource30.java by taking it out of functionTests/suites/DerbyNetClient.exclude. > 2) Run the test with client. > java -Dij.exceptionTrace=true -Dkeepfiles=true -Dframework=DerbyNetClient org.apache.derbyTesting.functionTests.harness.RunTest jdbcapi/checkDataSource30.java > 3) In a separate window, tail the test output until you see the line: > "DriverManager .execute() null - Invalid operation: statement close" > e.g. > tail -f derbynetclient/checkDataSource30.tmp > auto commit true > read only false > setTypeMap(EMPTY_MAP) - FAIL 0A000 - Feature not implemented: setTypeMap. > setTypeMap(null) - ok 0A000 - Feature not implemented: setTypeMap. > setTypeMap(map) - ok 0A000 - Feature not implemented: setTypeMap. > method calls on a closed connection > DriverManager .close() no error > DriverManager .createStatement() 08003 - No current connection. > DriverManager .execute() null - Invalid operation: statement close > 3) Abort the test run by pressing c > 4) Rerun the test without taking the server down > java -Dij.exceptionTrace=true -Dkeepfiles=true -Dframework=DerbyNetClient org.apache.derbyTesting.functionTests.harness.RunTest jdbcapi/checkDataSource30.java > The following exception will occur on create table and the database will be corrupt. > 2006-03-31 19:18:47.370 GMT Thread[DRDAConnThread_6,5,main] (XID = 200), (SESSIONID = 1), (DATABASE = wombat), (DRDAID = NF000001.G90E-1097469790362120575{12}), Cleanup action starting > 2006-03-31 19:18:47.370 GMT Thread[DRDAConnThread_6,5,main] (XID = 200), (SESSIONID = 1), (DATABASE = wombat), (DRDAID = NF000001.G90E-1097469790362120575{12}), Failed Statement is: create table y(i int) > ERROR XSAI2: The conglomerate (129) requested does not exist. > at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:311) > at org.apache.derby.impl.store.access.btree.index.B2IFactory.readConglomerate(B2IFactory.java:241) > at org.apache.derby.impl.store.access.RAMAccessManager.conglomCacheFind(RAMAccessManager.java:484) > at org.apache.derby.impl.store.access.RAMTransaction.findExistingConglomerate(RAMTransaction.java:389) > at org.apache.derby.impl.store.access.RAMTransaction.openConglomerate(RAMTransaction.java:1315) > at org.apache.derby.impl.sql.catalog.TabInfoImpl.insertRowListImpl(TabInfoImpl.java:525) > at org.apache.derby.impl.sql.catalog.TabInfoImpl.insertRow(TabInfoImpl.java:419) > at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorNow(DataDictionaryImpl.java:1637) > at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(DataDictionaryImpl.java:1624) > at org.apache.derby.impl.sql.execute.CreateTableConstantAction.executeConstantAction(CreateTableConstantAction.java:223) > at org.apache.derby.impl.sql.execute.MiscResultSet.open(MiscResultSet.java:56) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:361) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1160) > at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:567) > at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(EmbedStatement.java:158) > at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLIMM(DRDAConnThread.java:4395) > at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:645) > at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:236) > Cleanup action completed > Apache Derby Network Server - 10.2.0.0 alpha shutdown at 2006-03-31 19:18:48.601 GMT > Note: This tests hangs intermittently. When it does, it always hangs at the point mentioned in the reproduction for this issue. > Some relevant history regarding the test hang: > At revision 380672 I never saw the test hang > At revision 390481 I noticed it had started hanging consistently. > With the fix for DERBY-1144 the hang became intermittent. > The hang happens more on jdk 1.5 and jdk 1.6. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira