Hi Milosz Are you using a connection pool (commons dbcp) when you run the tests? Also are you using existing tables or creating new ones with each run?
On Wed, Sep 24, 2008 at 12:43 PM, Miłosz Tylenda <[EMAIL PROTECTED]> wrote: > Hello! > > When I run the OpenJPA test suite on DB2, it takes much more time to > complete than with other databases. The DB2 process hogs the CPU during the > test. A quite default installation of DB2 9.1 Express-C runs on the same > Linux (2.6.18-1.2798.fc6) laptop as OpenJPA 1.3.0-SNAPSHOT. Does anybody > have a clue what is the reason? Can it be related to the number of open > connections or schema generation? > > A log snippet follows. > > Running org.apache.openjpa.persistence.jdbc.meta.TestEJBCustomMapping > 3 TestConv INFO [main] openjpa.Runtime - Starting OpenJPA > 1.3.0-SNAPSHOT > 3499 TestConv INFO [main] openjpa.jdbc.JDBC - Using dictionary class > "org.apache.openjpa.jdbc.sql.DB2Dictionary" (DB2/LIN > UX SQL09010 ,IBM DB2 JDBC Universal Driver Architecture 3.1.57). > 3917 TestConv WARN [main] openjpa.MetaData - OpenJPA cannot map field " > org.apache.openjpa.persistence.jdbc.common.apps.Co > nstantJoinPC4.manyToMany" efficiently. It is of an unsupported type. The > field value will be serialized to a BLOB by default > . > 0 TestConv INFO [main] openjpa.Runtime - Starting OpenJPA > 1.3.0-SNAPSHOT > 2800 TestConv INFO [main] openjpa.jdbc.JDBC - Using dictionary class > "org.apache.openjpa.jdbc.sql.DB2Dictionary" (DB2/LIN > UX SQL09010 ,IBM DB2 JDBC Universal Driver Architecture 3.1.57). > 2844 TestConv WARN [main] openjpa.MetaData - OpenJPA cannot map field " > org.apache.openjpa.persistence.jdbc.common.apps.Co > nstantJoinPC4.manyToMany" efficiently. It is of an unsupported type. The > field value will be serialized to a BLOB by default > . > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 46.161 sec > > Regards, > Milosz > >
