[
https://issues.apache.org/jira/browse/OPENJPA-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18140904#comment-18140904
]
Maxim Solodovnik commented on OPENJPA-3028:
-------------------------------------------
there 2 last errors at MySQL:
{code}
2026-11-09T01:48:00.6117139Z 5 INFO [main] openjpa.jdbc.Schema - Executing
script
"file:/tmp/schemaGeneration/create_jpa_jpa22_se_generators_sequencegenerators.sql".
2026-11-09T01:48:00.6119993Z 7 WARN [main] openjpa.jdbc.Schema - Table
'openjpa_sequences_table' already exists {stmnt 242055469 CREATE TABLE
OPENJPA_SEQUENCES_TABLE (ID VARCHAR(255) NOT NULL, SEQUENCE_VALUE BIGINT,
PRIMARY KEY (ID)) ENGINE = innodb} [code=1050,
state=42S01]org.apache.openjpa.lib.jdbc.ReportingSQLException: Table
'openjpa_sequences_table' already exists {stmnt 242055469 CREATE TABLE
OPENJPA_SEQUENCES_TABLE (ID VARCHAR(255) NOT NULL, SEQUENCE_VALUE BIGINT,
PRIMARY KEY (ID)) ENGINE = innodb} [code=1050, state=42S01]
2026-11-09T01:48:00.6122712Z at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
2026-11-09T01:48:00.6123668Z at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203)
2026-11-09T01:48:00.6124958Z at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConnectionDecorator.java:955)
2026-11-09T01:48:00.6126141Z at
org.apache.openjpa.lib.jdbc.DelegatingStatement.executeUpdate(DelegatingStatement.java:123)
2026-11-09T01:48:00.6127056Z at
org.apache.openjpa.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:1610)
2026-11-09T01:48:00.6127879Z at
org.apache.openjpa.jdbc.schema.SchemaTool.executeScript(SchemaTool.java:740)
2026-11-09T01:48:00.6128569Z at
org.apache.openjpa.jdbc.schema.SchemaTool.run(SchemaTool.java:513)
2026-11-09T01:48:00.6129216Z at
org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:633)
2026-11-09T01:48:00.6129872Z at
org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:506)
2026-11-09T01:48:00.6130687Z at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:265)
2026-11-09T01:48:00.6131780Z at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:210)
2026-11-09T01:48:00.6132744Z at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:271)
2026-11-09T01:48:00.6133728Z at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
2026-11-09T01:48:00.6134521Z at
java.base/java.lang.reflect.Method.invoke(Method.java:580)
2026-11-09T01:48:00.6135429Z at
org.apache.openjpa.persistence.PersistenceProviderImpl.synchronizeMappings(PersistenceProviderImpl.java:323)
2026-11-09T01:48:00.6136548Z at
org.apache.openjpa.persistence.PersistenceProviderImpl.generateSchema(PersistenceProviderImpl.java:268)
2026-11-09T01:48:00.6137437Z at
jakarta.persistence.Persistence.generateSchema(Persistence.java:154)
2026-11-09T01:48:00.6138370Z at
ee.jakarta.tck.persistence.jpa22.se.generators.sequencegenerators.Client.sequenceGeneratorTest(Client.java:170)
2026-11-09T01:48:00.6139472Z at
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
2026-11-09T01:48:00.6140222Z at
java.base/java.lang.reflect.Method.invoke(Method.java:580)
{code}
> Jakarta Persistence 3.2 TCK failures on Derby, MySQL and SQL Server
> -------------------------------------------------------------------
>
> Key: OPENJPA-3028
> URL: https://issues.apache.org/jira/browse/OPENJPA-3028
> Project: OpenJPA
> Issue Type: Epic
> Reporter: Richard Zowalla
> Assignee: Richard Zowalla
> Priority: Major
> Attachments: run_de.tar.xz, run_ms.tar.xz, run_my.tar.xz,
> run_or.tar.xz
>
>
> Results of the Jakarta Persistence 3.2 TCK with
> {{openjpa-integration/tck/run-tck32.sh}} (reported by Maxim Solodovnik on
> dev@):
> * PostgreSQL 16: passed
> * MySQL 8.4.8: 2134 tests, 43 errors
> * SQL Server 2017-CU12: 2134 tests, 45 errors
> * Derby: 2134 tests, 184 errors
> The sub-tasks group the errors by cause. Several groups show up on more than
> one database. Where the TCK output only says "<test> failed", the cause still
> has to be found from the TCK logs.
> Note: the TCK build does not work with Maven 3.10.0; 3.9.x works.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
