Quarkus 3.36.0.CR1 released

[Guillaume Smet]

Hi,

We released Quarkus 3.36.0.CR1.

Changelog is here:
https://github.com/quarkusio/quarkus/releases/tag/3.36.0.CR1

Please try to upgrade your applications and report back:
- if everything is going well, just post a reply to this thread
- if you encounter issues, please open a GitHub issue in our tracker with a simple reproducer

We will build the final core artifacts next Wednesday.

Thanks!

--
The Quarkus dev team

[Paul C-B]

I have no idea why (still investigating) but bumping from 3.35.3 to
3.36.0.CR1 creates a number of deadlocks in our integration tests.

> --
> You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo_Z-ePVeLGbM2%3DgNVxGVxNVK9_y9P2oTcK5WTr7P5%3Dmvg%40mail.gmail.com.

[Guillaume Smet]

Hum. Doesn’t sound good. Keep us posted. Thanks!

> Le 14 mai 2026 à 23:26, Paul C-B <bcl...@gmail.com> a écrit :
>
> I have no idea why (still investigating) but bumping from 3.35.3 to

> To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CAMd%3DrQ8WK-oPVwsxCECfuHOjiCPDxvx5sWy_Zba1M1_Sy3K1-w%40mail.gmail.com.

[Paul C-B]

I think i found it. Even though we have
quarkus.datasource.jdbc.transaction-isolation-level=read-committed our
connections are using repeatable read. Agroal 3.1 has a change that
applies configured jdbcTransactionIsolation only while loading
defaults for the first physical connection. Subsequent connections
skip setTransactionIsolation, so Quarkus
quarkus.datasource.jdbc.transaction-isolation-level=read-committed is
not consistently applied.

https://github.com/quarkusio/quarkus/pull/54019

> To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/58380EED-E7A1-464F-BFA2-C61572594FB1%40gmail.com.

[Paul C-B]

https://github.com/agroal/agroal/compare/3.0.1...3.1?utm_source=chatgpt.com#diff-6d919acd392c1add2dc69d7cf6e829681b35aad1318eef01ae208cb4a948aeb0R264

[George Gastaldi]

Can you please open an issue and if possible attach a simple reproducer?

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CAMd%3DrQ8PuuXreBwvha%2Bd8Z%3DTsupB9P-7cK_tycfhjDnJnfdYMg%40mail.gmail.com.

[Paul C-B]

Will do. FYI its this specific change:

Once defaultHoldability is set, it guards any future connection from
having its isolation set

@SuppressWarnings( "MagicConstant" )
private void loadDefaults(Connection connection) throws SQLException {
if ( defaultHoldability == null ) {
synchronized ( jdbcProperties ) { // instead of "this",
use a private final field for internal synchronization
if ( defaultHoldability == null ) {
if (
configuration.jdbcTransactionIsolation().isDefined() ) {
connection.setTransactionIsolation(
configuration.jdbcTransactionIsolation().level() );
defaultIsolationLevel =
configuration.jdbcTransactionIsolation().level();
} else {
defaultIsolationLevel =
connection.getTransactionIsolation();
}
try { // set defaultHoldability last to establish
happens-before relationship
defaultHoldability = connection.getHoldability();
} catch ( SQLException e ) {
defaultHoldability = ResultSet.CLOSE_CURSORS_AT_COMMIT;

> To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CAK6y9v2Cz7pNixfpfcsyMSxSuRdvvHB8vKN39RK7M3McCkRs5g%40mail.gmail.com.

[gegas...@gmail.com]

Can you please give it a try with https://github.com/agroal/agroal/pull/190? I have it reproduced in a test already 😊

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CAMd%3DrQ_rhcpMF2MoqnkG%3DBk9kPgCCYgEv0NNK3OoKc%3DOjWGxYw%40mail.gmail.com.

[Paul C-B]

https://github.com/quarkusio/quarkus/issues/54243

> To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/ADD75B18-3A2B-244A-B016-FC9D333B4955%40hxcore.ol.

[gegas...@gmail.com]

Thank you, I confirm the PR fixes the problem. I’ll work with the Agroal team to have it released and have Quarkus patched ASAP.

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CAMd%3DrQ8BLKczF2hb%3DMJQjQMBgf83D9DEc8HZt8be_rDeuop6gg%40mail.gmail.com.

[Paul C-B]

Confirmed. And also in our full test suite. Thanks so much George

> To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/A81ACC36-15A7-8D43-962E-8FE34D53558D%40hxcore.ol.