db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Øystein Grøvlen (JIRA) <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-230) "Schema already exists" when creating a table
Date Wed, 01 Jun 2005 14:19:54 GMT
     [ http://issues.apache.org/jira/browse/DERBY-230?page=all ]

Øystein Grøvlen updated DERBY-230:
----------------------------------

    Attachment: derby-230b.diff

Attaching a new version of the patch where I have increased the probability of the test reproducing
the bug by increasing the number of threads to 200.  It now fails 16 out of 20 times on a
single-CPU machine.  Increasing the number of threads further seems to increase the execution
time very much.  Considering that when running derbyall, the test is run three times in different
frameworks, the probability of the test suite detecting the rebirth of this bug should be
more than 98%.  On a 2-CPU machine the test failed 20 out of 20 times.

> "Schema already exists" when creating a table
> ---------------------------------------------
>
>          Key: DERBY-230
>          URL: http://issues.apache.org/jira/browse/DERBY-230
>      Project: Derby
>         Type: Bug
>   Components: SQL
>     Versions: 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.0.0
>     Reporter: Øystein Grøvlen
>     Assignee: Øystein Grøvlen
>     Priority: Minor
>  Attachments: Main.java, derby-230b.diff
>
> When running a multithreaded program where several threads in parallell create tables
in a schema that is not explicitly created, one often get the following exception:
> ERROR X0Y68: Schema 'TESTSCHEMA' already exists.
>     at org.apache.derby.iapi.error.StandardException.newException(StandardException.java:322)
>     at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.duplicateDescriptorException(DataDictionaryImpl.java:1512)
>     at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptorNow(DataDictionaryImpl.java:1496)
>     at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addDescriptor(DataDictionaryImpl.java:1478)
>     at org.apache.derby.impl.sql.execute.CreateSchemaConstantAction.executeConstantAction(CreateSchemaConstantAction.java:147)
>     at org.apache.derby.impl.sql.execute.DDLConstantAction.getSchemaDescriptorForCreate(Unknown
Source)
>     at org.apache.derby.impl.sql.execute.CreateTableConstantAction.executeConstantAction(CreateTableConstantAction.java:213)
>     at org.apache.derby.impl.sql.execute.MiscResultSet.open(MiscResultSet.java:56)
>     at org.apache.derby.impl.sql.GenericPreparedStatement.execute(GenericPreparedStatement.java:366)
>     at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1108)
>     at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:517)
>     at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:475)
>     at derbytest.Main$CreateTable.run(Main.java:42)
>     at java.lang.Thread.run(Thread.java:595)
> A program that reproduces this bug will be attached.

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


Mime
View raw message