Hi Julian,

I'm trying run tests either "normal" (so with mongo) or with rdb in this way:

mvn clean install -PintegrationTesting -Prdb-mariadb -Dnsfixtures=DOCUMENT_RDB 
-Drdb.jdbc-url=jdbc:mariadb://localhost:8080/oak -Drdb.jdbc-user=root 
-Drdb.jdbc-passwd=geheim -Dmax.jar.size=200000000 -Dtest=ContentSessionTest 
-Dmaven.surefire.debug

In both ways I have almost always test failures... sometimes one test sometimes 
a different one, for example:

[ERROR] Failures:
[ERROR]   CacheActionDispatcherTest.testQueue:96 Following actions hasn't been 
executed: [1_8, 1_9, 1_10, 1_11, 1_12, 1_13, 1_14, 1_15, 1_16, 1_17, 1_18, 
1_19, 1_20, 1_21, 1_22, 1_23, 1_24, 1_25, 1_26, 1_27, 1_28, 1_29, 1_30, 1_31, 
1_32, 1_33, 1_34, 1_35, 1_36, 1_37, 1_38, 1_39, 1_40, 1_41, 1_42, 1_43, 1_44, 
1_45, 1_46, 1_47, 1_48, 1_49, 1_50, 1_51, 1_52, 1_53, 1_54, 1_55, 1_56, 1_57, 
1_58, 1_59, 1_60, 1_61, 1_62, 1_63, 1_64, 1_65, 1_66, 1_67, 1_68, 1_69, 1_70, 
1_71, 1_72, 1_73, 1_74, 1_75, 1_76, 1_77, 1_78, 1_79, 1_80, 1_81, 1_82, 1_83, 
1_84, 1_85, 1_86, 1_87, 1_88, 1_89, 1_90, 1_91, 1_92, 1_93, 1_94, 1_95, 1_96, 
1_97, 1_98, 1_99]
[INFO]
[ERROR] Tests run: 2343, Failures: 1, Errors: 0, Skipped: 210

So I'm in difficulty to evaluate if what I'm doing is ok

I've already taken last commits which I've seen there was some junit fix


Cordiali saluti / Best regards,

Raffaele Gambelli
Senior Java Developer
E  [email protected]<mailto:[email protected]>

[CEGEKA]        Via Ettore Cristoni, 84
IT-40033 Bologna (IT),Italy
T +39 02 2544271
WWW.CEGEKA.COM<https://www.cegeka.com/>

[https://2655225.fs1.hubspotusercontent-na1.net/hubfs/2655225/0.0%20Cegeka%20(new)/1.%20Visuals/Email%20Signatures/Annual_Report_Visuals_2023_Email%20Banner%201.png]<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>
<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>

Dichiarazione di 
Riservatezza<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>

Le informazioni contenute nella mail sono riservate. Se si rende conto di non 
essere il destinatario corretto della mail, la preghiamo di segnalare l'errore 
al mittente e di cancellare immediatamente il messaggio. L’utilizzo improprio 
di informazioni riservate può comportare 
sanzioni.<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>

Protezione dei dati 
personali<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>

La informiamo che i suoi dati saranno trattati da Cegeka nel rispetto delle 
disposizioni di legge applicabili (D. Lgs 196/2003 e Regolamento UE 679/2016). 
Per maggiori dettagli può consultare le nostre informative privacy al link 
<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>
 https://www.cegeka.com/it/informazioni-sulla-privacy. 
<https://www.cegeka.com/it/informazioni-sulla-privacy>

________________________________
From: Julian Reschke <[email protected]>
Sent: Friday, October 11, 2024 7:50 PM
To: [email protected] <[email protected]>
Subject: Re: Problems in using RDB DocumentStore on mariadb

On 11.10.2024 11:59, Raffaele Gambelli wrote:
> The transaction isolation level, at least for MariaDB you can set in the 
> command run line, for example in this way:
>
> mysqld --lower-case-table-names=1 --character-set-server=utf8 
> --collation-server=utf8_unicode_ci --transaction-isolation=READ-COMMITTED 
> --max-allowed-packet=128M --max_connections=250
>
> While character-set and collation can be set at db level, the transaction 
> isolation level can be set globally or at session level.
>
> Best regards

FWIW, when I last touched the documentation, I wrote
inhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjackrabbit.apache.org%2Foak%2Fdocs%2Fnodestore%2Fdocument%2Frdb-document-store.html%23mysql&data=05%7C02%7CRaffaele.Gambelli%40cegeka.com%7C961832b3d9b246e2ffb208dcea1d7a18%7C42151053019347aa9e81effd81f772cc%7C0%7C0%7C638642659551886768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=GhragGboRQVb5qz4h2lQH0aineuqZ4w0gJynNpBBDsc%3D&reserved=0:

> To verify, check the INFO level log message written by RDBDocumentStore upon 
> startup. For example:
>
> 13:40:46.637 INFO  [main] RDBDocumentStore.java:1065        RDBDocumentStore 
> (SNAPSHOT) instantiated for database MySQL 8.0.15 (8.0), using driver: MySQL 
> Connector/J mysql-connector-java-8.0.15 (Revision: 
> 79a4336f140499bd22dd07f02b708e163844e3d5) (8.0), connecting to: 
> jdbc:mysql://localhost:3306/oak?serverTimezone=UTC, properties: 
> {character_set_database=utf8mb4, character_set_client=utf8mb4, 
> character_set_connection=utf8mb4, character_set_results=, 
> max_allowed_packet=8388608, collation_database=utf8mb4_unicode_ci, 
> character_set_system=utf8, collation_server=utf8mb4_0900_ai_ci, 
> collation=utf8mb4_unicode_ci, character_set_filesystem=binary, 
> character_set_server=utf8mb4, collation_connection=utf8mb4_0900_ai_ci}, 
> transaction isolation level: TRANSACTION_REPEATABLE_READ (4), .nodes: ID 
> VARBINARY(512), MODIFIED BIGINT(20), HASBINARY SMALLINT(6), DELETEDONCE 
> SMALLINT(6), MODCOUNT BIGINT(20), CMODCOUNT BIGINT(20), DSIZE BIGINT(20), 
> VERSION SMALLINT(6), SDTYPE SMALLINT(6), SDMAXREVTIME BIGINT(20), DATA 
> VARCHAR(16000), BDATA LONGBLOB(2147483647) /* {BIGINT=-5, LONGBLOB=-4, 
> SMALLINT=5, VARBINARY=-3, VARCHAR=12} */ /* unique index oak.PRIMARY on nodes 
> (ID ASC) other (#0, p0), index oak.NODES_MOD on nodes (MODIFIED ASC) other 
> (#0, p0), index oak.NODES_SDM on nodes (SDMAXREVTIME ASC) other (#0, p0), 
> index oak.NODES_SDT on nodes (SDTYPE ASC) other (#0, p0), index oak.NODES_VSN 
> on nodes (VERSION ASC) other (#0, p0) */


So even back then, we just used "TRANSACTION_REPEATABLE_READ (4)".

Best regards, Julian


Reply via email to