Bug 264598 - Some testSetup failed within jpa.advanced on server with "name is already used by an existing object" exception
Summary: Some testSetup failed within jpa.advanced on server with "name is already use...
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords: test
Depends on:
Blocks:
 
Reported: 2009-02-11 16:19 EST by Kevin Yuan CLA
Modified: 2022-06-09 10:31 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Yuan CLA 2009-02-11 16:19:16 EST 
These tests failed only in EclipseLink 2.0 because of the tests change in setup, need to fix the following parts:

    public void testSetup() {
        new AdvancedTableCreator().replaceTables(JUnitTestCase.getServerSession());
        new CompositePKTableCreator().replaceTables(JUnitTestCase.getServerSession());
        clearCache();
    }

The following are exceptions:
Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object Error Code: 955

Local Exception Stack: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.0.20090211-SNAPSHOT): org.eclipse.persistence.exceptions.DatabaseExceptionInternal Exception: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing objectError Code: 955 at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:313) at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:767) at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:833) at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:558) at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:501) at org.eclipse.persistence.sessions.server.ServerSession.executeCall(ServerSession.java:536) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:205) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:191) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeNoSelectCall(DatasourceCallQueryMechanism.java:234) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeNoSelect(DatasourceCallQueryMechanism.java:214) at org.eclipse.persistence.queries.DataModifyQuery.executeDatabaseQuery(DataModifyQuery.java:85) at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:664) at org.eclipse.persistence.internal.sessions.AbstractSession.internalExecuteQuery(AbstractSession.java:2247) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1185) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1169) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1129) at org.eclipse.persistence.internal.sessions.AbstractSession.executeNonSelectingCall(AbstractSession.java:898) at org.eclipse.persistence.tools.schemaframework.DatabaseObjectDefinition.createOnDatabase(DatabaseObjectDefinition.java:81) at org.eclipse.persistence.tools.schemaframework.SchemaManager.createObject(SchemaManager.java:187) at org.eclipse.persistence.tools.schemaframework.SchemaManager.replaceObject(SchemaManager.java:882) at org.eclipse.persistence.tools.schemaframework.TableCreator.replaceTablesAndConstraints(TableCreator.java:297) at org.eclipse.persistence.tools.schemaframework.TableCreator.replaceTables(TableCreator.java:248) at org.eclipse.persistence.tools.schemaframework.TableCreator.replaceTables(TableCreator.java:240) at org.eclipse.persistence.testing.tests.jpa.advanced.compositepk.AdvancedCompositePKJunitTest.testSetup(AdvancedCompositePKJunitTest.java:69) at org.eclipse.persistence.testing.framework.junit.JUnitTestCase.runBareServer(JUnitTestCase.java:396) at org.eclipse.persistence.testing.framework.server.TestRunnerBean.runTest(TestRunnerBean.java:87)
Comment 1 Kevin Yuan CLA 2009-02-12 11:17:52 EST 
This is new regression since the following checkin by Chris:
SVN Checkin: Bug 241765 - JPA 2.0 Derived identities
https://bugs.eclipse.org/bugs/show_bug.cgi?id=241765
reviewed by Gordon and Guy
Comment 2 Kevin Yuan CLA 2009-02-12 14:34:20 EST 
Several JPA test suites use the same table creator and call "new AdvancedTableCreator().replaceTables(JUnitTestCase.getServerSession());" in each of them, and it failed intermittently on running all of them together. Need to dig into it.
It could be something to do with failing tests on the server not cleaning up resources, since the testSetup tests that fail seem to follow closely other tests that fail.
Comment 3 Kevin Yuan CLA 2009-07-10 09:35:02 EDT 
After OptimisticLock issue fix (the bug 264582), this issue also has been fixed.
Comment 4 Peter Krogh CLA 2009-08-26 09:47:45 EDT 
Mass update to change fixed in target.
Comment 5 Peter Krogh CLA 2009-08-26 09:50:12 EDT 
Mass update to change fixed in target.
Comment 6 Peter Krogh CLA 2009-08-26 09:55:43 EDT 
Mass update to change fixed in target.
Comment 7 Peter Krogh CLA 2009-08-26 09:58:00 EDT 
Mass update to change fixed in target.
Comment 8 Eclipse Webmaster CLA 2022-06-09 10:31:46 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink