Skip to content

Commit 3ab736f

Browse files
authored
Merge pull request #124 from Ladicek/smallrye-fault-tolerance-6.9.2
SmallRye Fault Tolerance 6.9.2 release announcement
2 parents 6ac3df7 + 153f473 commit 3ab736f

1 file changed

Lines changed: 24 additions & 0 deletions

File tree

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
:page-layout: post
2+
:page-title: Fault Tolerance 6.9.2
3+
:page-synopsis: SmallRye Fault Tolerance 6.9.2 released!
4+
:page-tags: [announcement, microprofile]
5+
:page-date: 2025-07-31 15:00:00.000 +0100
6+
:page-author: lthon
7+
:smallrye-ft: SmallRye Fault Tolerance
8+
:microprofile-ft: MicroProfile Fault Tolerance
9+
10+
= Fault Tolerance 6.9.2
11+
12+
Today, we announce the https://github.com/smallrye/smallrye-fault-tolerance/releases/tag/6.9.2[release] of {smallrye-ft} 6.9.2.
13+
This release contains an important bugfix.
14+
15+
Since the link:/blog/fault-tolerance-6-7-2[6.7.2] and link:/blog/fault-tolerance-6-7-3/[6.7.3] releases, Vert.x worker threads are treated as event loops as well.
16+
In case of a worker thread execution from an event loop context, the event loop integration code used to use `Context.executeBlocking()` in an ordered fashion.
17+
This may lead to a deadlock-like situation in case the original call also occurs in an ordered `executeBlocking()` situation, because:
18+
19+
. the original handler that called a guarded method may wait for it to complete,
20+
. the newly scheduled handler comes after the original handler, so has to wait for it to complete.
21+
22+
In this release, the issue is fixed: the event loop integration code no longer requires ordering.
23+
24+
As usual, if you have any ideas for improvements, please https://github.com/smallrye/smallrye-fault-tolerance/issues[file an issue]!

0 commit comments

Comments
 (0)