# Quarkus - Supersonic Subatomic Java

Quarkus: Supersonic Subatomic Java

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Java4Shell (CVE-2026-114938): Status and mitigation for Quarkus users

DevFeed: [Java4Shell (CVE-2026-114938): Status and mitigation for Quarkus users](<https://devfeed.tech/articles/java4shell-cve-2026-114938-status-and-mitigation-for-quarkus-users-140976.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/java4shell/>)

Author: Clement Escoffier (https://twitter.com/clementplop)

Published: 2026-11-18T00:00:00Z

Content type: news

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [openjdk](<https://devfeed.tech/topics/openjdk.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [redhat ubi](<https://devfeed.tech/topics/redhat-ubi.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2026](<https://devfeed.tech/tags/2026.md>), [avx](<https://devfeed.tech/tags/avx.md>), [avx-512-vbmi](<https://devfeed.tech/tags/avx-512-vbmi.md>), [bare-metal](<https://devfeed.tech/tags/bare-metal.md>), [base64](<https://devfeed.tech/tags/base64.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [bug](<https://devfeed.tech/tags/bug.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [container](<https://devfeed.tech/tags/container.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [decode](<https://devfeed.tech/tags/decode.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [mitigation](<https://devfeed.tech/tags/mitigation.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [status](<https://devfeed.tech/tags/status.md>)

### AI overview

Java4Shell is a JDK Base64 decoder memory corruption flaw; Quarkus itself is not affected, and upgrading Quarkus does not fix it. Exploitation requires an unpatched listed OpenJDK build, an x86-64 CPU with AVX-512 VBMI, enabled Base64 intrinsics, and decoding attacker-controlled input. For bare-metal JVMs, install a fixed JDK or use `-XX:-UseBASE64Intrinsics` until patched. UBI Java runtime images were still unfixed in the post's 18 November 2026 update; add the flag through `JAVA_OPTS_APPEND` to preserve image defaults. Mandrel native executables are unaffected. Patched Mandrel builder images need floating tags re-pulled or pinned tags updated; overriding `JAVA_TOOL_OPTIONS` can remove their workaround. Verify the running JVM reports `UseBASE64Intrinsics = false` with `jcmd`.

### Source excerpt

This post is updated as the situation evolves. Last updated: 18 November 2026, 18:00 UTC TL;DR / Current status Quarkus is not affected. The JDK is. Native executables built with Mandrel are not affected. Mandrel builder images: patched (workaround applied). Re-pull floating tags. Update pinned tags. See the available tags. UBI Java runtime images: not yet fixed. Add -XX:-UseBASE64Intrinsics to the JVM options as workaround. JVM on bare metal: if your JDK is patched, you are fine. Otherwise, add -XX:-UseBASE64Intrinsics as workaround. Deployment model Status Action JVM on bare metal Depends on your JDK Upgrade the JDK, or add -XX:-UseBASE64Intrinsics JVM in a container, UBI Java runtime image ⚠ Not fixed yet Add -XX:-UseBASE64Intrinsics to JAVA_OPTS_APPEND Native executable (Mandrel) ✅ Not affected None Mandrel builder images ✅ Patched Re-pull floating tags, update pinned tags The vulnerability CVE-2026-114938, aka "Java4Shell", is a memory corruption bug in the OpenJDK Base64 decoder. The JVM uses a CPU-optimized implementation (an intrinsic) to decode Base64. A crafted Base64 input makes it write past its buffer. Researchers demonstrated memory disclosure and remote code execution. Exploitation requires all of the following: An unpatched OpenJDK 17.0.6+, 21, 25 or 27 build (all vendors: Temurin, Red Hat, Corretto, Zulu, etc.). An x86-64 CPU exposing AVX-512 VBMI (on Linux: avx512f, avx512bw, avx512vbmi and bmi2 in /proc/cpuinfo). ARM64 is not affected. Base64 intrinsics enabled (the default). The application decodes attacker-controlled Base64 data. Almost every HTTP application does decode Base64: Basic auth headers, JWTs, request payloads. Oracle rates it CVSS 3.1 8.1. No exploitation in the wild is known at the time of writing. References: Tenable FAQ Keycloak advisory Is Quarkus affected? No. The bug lives in the JDK, not in Quarkus. Upgrading Quarkus does not fix it. Fixing or mitigating the JDK does. Mitigation per deployment model JVM on bare metal You run

## Break your dependencies on purpose: introducing Quarkus Resiliency Testing

DevFeed: [Break your dependencies on purpose: introducing Quarkus Resiliency Testing](<https://devfeed.tech/articles/break-your-dependencies-on-purpose-introducing-quarkus-resiliency-testing-135957.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-resiliency-testing/>)

Author: Georgios Andrianakis (https://twitter.com/geoand86)

Published: 2026-11-12T00:00:00Z

Content type: tutorial

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [connection pool](<https://devfeed.tech/topics/connection-pool.md>)

Tags: [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [database](<https://devfeed.tech/tags/database.md>), [docker](<https://devfeed.tech/tags/docker.md>), [examples](<https://devfeed.tech/tags/examples.md>), [exception](<https://devfeed.tech/tags/exception.md>), [exceptions](<https://devfeed.tech/tags/exceptions.md>), [extension](<https://devfeed.tech/tags/extension.md>), [failure](<https://devfeed.tech/tags/failure.md>), [fallback](<https://devfeed.tech/tags/fallback.md>), [fault-injection](<https://devfeed.tech/tags/fault-injection.md>), [inventory](<https://devfeed.tech/tags/inventory.md>), [junit](<https://devfeed.tech/tags/junit.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [resiliency](<https://devfeed.tech/tags/resiliency.md>), [retries](<https://devfeed.tech/tags/retries.md>), [services](<https://devfeed.tech/tags/services.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Quarkus Resiliency Testing injects network and resource failures into `@QuarkusTest` runs so real clients and application configuration face hangs, broken responses, and unavailable dependencies. `NetworkFaultsProfile` routes supported outbound connections through in-process proxies; tests can check bounded waits and recovery, bulkheads, payment retries with stable idempotency keys, JDBC timeouts and pool exhaustion, stale connections, transaction rollback, and Kafka publishing behavior. The examples show that retries, timeouts, exception mapping, and transaction choices determine customer-visible outcomes; fault injection alone does not provide resilience. The article also describes disk-full and DNS faults, Dev UI exploration, and an outbox alternative when orders must be accepted during Kafka outages. Requirements include Quarkus 4 and Java 21. Limits include plaintext HTTP/1.x for HTTP faults, Linux-only `connectTimeout()`, and no `@QuarkusIntegrationTest` support; some Dev Services still require Docker.

### Source excerpt

Imagine a customer placing an order. Your service reserves stock, charges their card, and stores the result. On a normal day, each step takes milliseconds and the customer sees a confirmation. Now imagine inventory accepts the connection but never answers. Or the payment provider charges the card just before the connection breaks. Or the database stops responding while your application is holding a connection from its pool. These failures demand different responses. Waiting longer can use up your workers; retrying can charge the customer twice; catching an exception does nothing if the client never throws one. A happy-path test tells you little about any of them. Quarkus Resiliency Testing lets you reproduce these conditions in a @QuarkusTest, using your application's real clients and configuration. Let's follow that order through four failure scenarios and turn each one into a test. The examples are excerpts from the resilient-orders sample, which includes the endpoints, supporting classes and complete tests. Put the failure on the wire Add the test dependency: <dependency> <groupId>io.quarkiverse.resiliencytesting</groupId> <artifactId>quarkus-resiliency-testing-junit</artifactId> <version>0.6.0</version> <scope>test</scope> </dependency> With NetworkFaultsProfile, the extension discovers supported outbound connections from Quarkus configuration, including Dev Services, and redirects them through proxies inside the test JVM. The proxy normally relays traffic. During a fault, the real client encounters the broken connection and reacts with its own timeouts, retries and exceptions. A mock that throws an exception can check a fallback; this also exercises the client configuration that determines whether, and when, that fallback is reached. The fault injection needs no separate container or sidecar; dependencies such as the sample's PostgreSQL Dev Service can still need Docker. 1. Inventory stops answering The customer clicks "Place order", but inventory never respond

## Hear your application with Quarkus Sonify

DevFeed: [Hear your application with Quarkus Sonify](<https://devfeed.tech/articles/hear-your-application-with-quarkus-sonify-126440.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-sonify/>)

Author: Fouad Almalki (https://twitter.com/engineer\_fouad)

Published: 2026-11-10T00:00:00Z

Content type: tutorial

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [cURL](<https://devfeed.tech/topics/curl.md>)

Tags: [delete](<https://devfeed.tech/tags/delete.md>), [dev](<https://devfeed.tech/tags/dev.md>), [extension](<https://devfeed.tech/tags/extension.md>), [fun](<https://devfeed.tech/tags/fun.md>), [http](<https://devfeed.tech/tags/http.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [native](<https://devfeed.tech/tags/native.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>)

### AI overview

Quarkus Sonify makes development activity audible: it plays distinct sounds for incoming HTTP methods and outgoing status codes, plus a chime at startup and after live reloads. Sounds are synthesized in the JVM on the machine running the application, requiring no browser tab or native dependency. Add the extension and run the app in dev mode; CDI methods can trigger custom sounds with @PlaySound, or code can inject SoundPlayer and call play(). WAV files can replace sounds, and individual sounds can be disabled through application.properties. Quarkus adds the audio artifact only in dev mode; in production and tests, the annotation and SoundPlayer do nothing and the audio code is absent.

### Source excerpt

In dev mode, you learn what your application does by looking: at the terminal, at the browser, at the Dev UI. Quarkus Sonify lets you listen instead. It is a small extension, and it is mostly for fun. What you hear Sonify plays a short sound on the machine that runs the application: one when an HTTP request arrives, different for each HTTP method one when its response is sent, different for each status code a chime when the application starts, and after every live reload A GET is one tap, a POST is two rising taps, and a DELETE is two falling taps. For a response, the class of the status code picks the kind of sound, and the code picks its pitch: a 200 is a clear note, a 404 is a hollow one, and a 500 is a thud. The sounds are synthesized in the JVM, so there is no browser tab to keep open and no native dependency. Try it Add the extension to your application: <dependency> <groupId>io.quarkiverse.sonify</groupId> <artifactId>quarkus-sonify</artifactId> <version>0.1.0</version> </dependency> Start dev mode, and send a request: curl -X DELETE http://localhost:8080/no-such-thing Your own sounds A method of a CDI bean can have a sound of its own: @PlaySound("order-placed") public Order place(Cart cart) { // ... } You can also inject a SoundPlayer and call play("order-placed") from anywhere. Every sound can be replaced with a WAV file or turned off in application.properties: quarkus.sonify.sound."order-placed"=sounds/coin.wav quarkus.sonify.status."418"=sounds/whistle.wav quarkus.sonify.method.options=off Only in dev mode Everything that makes a sound lives in an artifact that Quarkus only adds in dev mode. In production and in tests, the annotation and the SoundPlayer do nothing, and the audio code is not part of the application. There is nothing to remove before you ship. Listen for yourself The repository has a demo with a page of links, one for every HTTP method and status code. Ideas for sounds are welcome in the issue tracker.

## Quarkus 3.33.4.2 released - LTS emergency release

DevFeed: [Quarkus 3.33.4.2 released - LTS emergency release](<https://devfeed.tech/articles/quarkus-3-33-4-2-released-lts-emergency-release-126438.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-3-33-4-2-released/>)

Author: Guillaume Smet (https://twitter.com/gsmet\_)

Published: 2026-11-09T00:00:00Z

Content type: release

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Release notes](<https://devfeed.tech/topics/release-notes.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [release engineering](<https://devfeed.tech/topics/release-engineering.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [brotli](<https://devfeed.tech/tags/brotli.md>), [brotli-decoder](<https://devfeed.tech/tags/brotli-decoder.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [community](<https://devfeed.tech/tags/community.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-110879](<https://devfeed.tech/tags/cve-2026-110879.md>), [cve-2026-111497](<https://devfeed.tech/tags/cve-2026-111497.md>), [cves](<https://devfeed.tech/tags/cves.md>), [decoder](<https://devfeed.tech/tags/decoder.md>), [emergency](<https://devfeed.tech/tags/emergency.md>), [execution](<https://devfeed.tech/tags/execution.md>), [heap](<https://devfeed.tech/tags/heap.md>), [http](<https://devfeed.tech/tags/http.md>), [lts](<https://devfeed.tech/tags/lts.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [release](<https://devfeed.tech/tags/release.md>)

### AI overview

Quarkus 3.33.4.2 is an emergency release for the 3.33 LTS stream. It fixes an authorization bypass in the Quarkus Vert.x HTTP management interface, a Jackson Databind PolymorphicTypeValidator bypass (noted as an incomplete fix for CVE-2026-54512), and a Brotli decoder out-of-bounds write that could lead to remote code execution. Jackson 2.21.8 also resolves CVEs in Avro, CBOR, Protobuf, and Smile dataformat modules managed by the Quarkus BOM. The release is described as a safe upgrade for users already on 3.33. To update, use the latest Quarkus CLI and run `quarkus update --stream=3.33`; the text says this command can migrate applications from any Quarkus version, including 2.x.

### Source excerpt

Today, we released Quarkus 3.33.4.2, an emergency release for the 3.33 LTS stream. This release fixes the following CVEs: CVE-2026-107912 - Quarkus Vert.x HTTP: Authorization bypass in the management interface due to incorrect combination of the management root path with permission rules CVE-2026-110879 - Jackson Databind: PolymorphicTypeValidator bypass via generic type parameters and array element types of type ids (incomplete fix for CVE-2026-54512) CVE-2026-111497 - Brotli (via Brotli4J): Heap out-of-bounds write in the Brotli decoder leading to remote code execution Everything else resolved by Jackson 2.21.8 (CVEs in the Avro, CBOR, Protobuf and Smile dataformat modules, which are not part of Quarkus itself but are managed by the Quarkus BOM) It should be a safe upgrade for anyone already using 3.33. Update To update to Quarkus 3.33, we recommend updating to the latest version of the Quarkus CLI and run: quarkus update --stream=3.33 Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.33. Full changelog You can get the full changelog of 3.33.4.2 on GitHub. Come Join Us We value your feedback a lot so please report bugs, ask for improvements... Let's build something great together! If you are a Quarkus user or just curious, don't be shy and join our welcoming community: provide feedback on GitHub; craft some code and push a PR; discuss with us on Zulip and on the mailing list; ask your questions on Stack Overflow.

## Quarkus Insights #267: Sandboxing agents with Quarkus, for Quarkus

DevFeed: [Quarkus Insights #267: Sandboxing agents with Quarkus, for Quarkus](<https://devfeed.tech/articles/quarkus-insights-267-sandboxing-agents-with-quarkus-for-quarkus-129274.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-insights-267-sandboxing-agents-with-quarkus-for-quarkus/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-11-09T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [insights](<https://devfeed.tech/tags/insights.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [sandboxing](<https://devfeed.tech/tags/sandboxing.md>)

### AI overview

isx gives each coding agent a disposable Incus system container, allowing it to install packages and run services without access to the host's files or credentials. A host proxy injects real credentials into intercepted requests, while Git integration lets the user fetch, inspect, and sign agent work before opening a pull request. Machines start in about 400 ms on the presenter's Linux laptop; macOS instead runs the stack inside one VM, and Windows is not yet supported. The project also supports coordinating agents through template allow lists and uses checksum checks to validate cached artifacts. The presenter frames isx as a hobby project for preventing well-intentioned mistakes, not as protection against a determined malicious AI.

### Source excerpt

This summary was generated using AI, reviewed by humans - watch the video for the full story. Quarkus Insights #267: Sandboxing agents with Quarkus, for Quarkus The promise of coding agents is that you hand over a task, walk away, and come back to finished work. In practice, many developers spend their day pressing "yes" on permission prompts. In episode 267, Sanne Grinovero, one of the earliest Quarkus contributors, joins hosts Eric Deandrea and Holly Cummins to present isx, a tool he built on Quarkus that gives each agent its own disposable machine so it can run with full autonomy while your keys, files, and production credentials stay out of reach. Quarkus News Holly noted that Quarkus 4 Beta 3 is out and that CR1 is expected this week. She also reminded everyone that Quarkus:Dev is coming in early February, with the call for papers opening soon. Three Questions About Quarkus and AI Holly explained that questions about Quarkus and AI tend to fall into three groups: Embedding AI in applications: The answer is LangChain4j with the Quarkus integration. Using AI to build applications better: This covers the AI development experience, including the Quarkus MCP server and work by Eric and others to expose only the documentation that matches the extensions configured in your application. How the Quarkus team itself uses AI: isx is one answer to that question, and it is also a Quarkus use case because the tool is built on Quarkus. Sanne introduced himself as a contributor from the early days, when the group was prototyping ideas such as running Hibernate in native images. Today he splits his time between Quarkus and other projects, and acts as a link between Quarkus and the OpenJDK engineers so that each side benefits from what the other is building. He stressed that isx is a hobby project rather than an official direction of the Quarkus team, although several team members, including Holly, already use it daily. The Problem: Approval Fatigue Sanne described the typical f

## Quarkus 3.40.1.2 released - LTS emergency release

DevFeed: [Quarkus 3.40.1.2 released - LTS emergency release](<https://devfeed.tech/articles/quarkus-3-40-1-2-released-lts-emergency-release-126439.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-3-40-1-2-released/>)

Author: Guillaume Smet (https://twitter.com/gsmet\_)

Published: 2026-11-09T00:00:00Z

Content type: release

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [Release notes](<https://devfeed.tech/topics/release-notes.md>), [Dynamic authorization rules](<https://devfeed.tech/topics/dynamic-authorization-rules.md>)

Tags: [authorization](<https://devfeed.tech/tags/authorization.md>), [brotli](<https://devfeed.tech/tags/brotli.md>), [brotli-decoder](<https://devfeed.tech/tags/brotli-decoder.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-110879](<https://devfeed.tech/tags/cve-2026-110879.md>), [cve-2026-111497](<https://devfeed.tech/tags/cve-2026-111497.md>), [emergency](<https://devfeed.tech/tags/emergency.md>), [http](<https://devfeed.tech/tags/http.md>), [interface](<https://devfeed.tech/tags/interface.md>), [jackson](<https://devfeed.tech/tags/jackson.md>), [jackson-databind](<https://devfeed.tech/tags/jackson-databind.md>), [lts](<https://devfeed.tech/tags/lts.md>), [out-of-bounds-write](<https://devfeed.tech/tags/out-of-bounds-write.md>), [permission](<https://devfeed.tech/tags/permission.md>), [protobuf](<https://devfeed.tech/tags/protobuf.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [release](<https://devfeed.tech/tags/release.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [resolved](<https://devfeed.tech/tags/resolved.md>)

### AI overview

Quarkus 3.40.1.2 is an emergency update for the 3.40 LTS stream. It fixes an authorization bypass in the Vert.x HTTP management interface, a Jackson Databind PolymorphicTypeValidator bypass (an incomplete fix for CVE-2026-54512), and a Brotli decoder heap out-of-bounds write that could enable remote code execution. Jackson 2.21.8 also resolves CVEs in Avro, CBOR, Protobuf, and Smile dataformat modules managed by the Quarkus BOM. The release is described as a safe upgrade for users already on 3.40. The recommended update command is `quarkus update --stream=3.40`; the CLI can also update applications from earlier Quarkus versions, including 2.x.

### Source excerpt

Today, we released Quarkus 3.40.1.2, an emergency release for the 3.40 LTS stream. This release fixes the following CVEs: CVE-2026-107912 - Quarkus Vert.x HTTP: Authorization bypass in the management interface due to incorrect combination of the management root path with permission rules CVE-2026-110879 - Jackson Databind: PolymorphicTypeValidator bypass via generic type parameters and array element types of type ids (incomplete fix for CVE-2026-54512) CVE-2026-111497 - Brotli (via Brotli4J): Heap out-of-bounds write in the Brotli decoder leading to remote code execution Everything else resolved by Jackson 2.21.8 (CVEs in the Avro, CBOR, Protobuf and Smile dataformat modules, which are not part of Quarkus itself but are managed by the Quarkus BOM) It should be a safe upgrade for anyone already using 3.40. Update To update to Quarkus 3.40, we recommend updating to the latest version of the Quarkus CLI and run: quarkus update --stream=3.40 Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.40. Full changelog You can get the full changelog of 3.40.1.2 on GitHub. Come Join Us We value your feedback a lot so please report bugs, ask for improvements... Let's build something great together! If you are a Quarkus user or just curious, don't be shy and join our welcoming community: provide feedback on GitHub; craft some code and push a PR; discuss with us on Zulip and on the mailing list; ask your questions on Stack Overflow.

## Debates, voting, and reflection loops: composing an agentic PR reviewer that costs less than a dollar

DevFeed: [Debates, voting, and reflection loops: composing an agentic PR reviewer that costs less than a dollar](<https://devfeed.tech/articles/debates-voting-and-reflection-loops-composing-an-agentic-pr-reviewer-that-costs-less-than-a-dollar-116297.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/agentic-pr-reviewer/>)

Author: Mario Fusco (https://twitter.com/mariofusco)

Published: 2026-11-04T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [agent orchestration](<https://devfeed.tech/topics/agent-orchestration.md>), [Agentic AI](<https://devfeed.tech/topics/what-is-agentic-ai.md>), [llm-reasoning](<https://devfeed.tech/topics/llm-reasoning.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>)

Tags: [abstraction](<https://devfeed.tech/tags/abstraction.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [budget](<https://devfeed.tech/tags/budget.md>), [chat](<https://devfeed.tech/tags/chat.md>), [comment](<https://devfeed.tech/tags/comment.md>), [confidence](<https://devfeed.tech/tags/confidence.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [decision-model](<https://devfeed.tech/tags/decision-model.md>), [decision-models](<https://devfeed.tech/tags/decision-models.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [loops](<https://devfeed.tech/tags/loops.md>), [pr](<https://devfeed.tech/tags/pr.md>), [reflection](<https://devfeed.tech/tags/reflection.md>), [voting](<https://devfeed.tech/tags/voting.md>)

### AI overview

The reviewer combines a deterministic Quarkus sequence with model-driven routing and judgment: a decision model selects relevant specialists, while code handles fetching, finding validation, score calibration, and report assembly. Conditional coverage reviews, chunking for large diffs, debates for uncertain findings, voting for borderline scores, and a capped reflection loop add extra review only when triggered. It uses tiered models, retries transient failures, and discloses skipped work; a read-only GitHub token and human approval keep the process bounded. On the reported 2,900-line, 56-file pull request, it took 5 minutes 49 seconds and cost $0.45. It found a source-compatibility issue, rejected a disputed binary-compatibility finding, and exposed a weak report critic that failed to improve its score across three rounds.

### Source excerpt

At the moment when I write this, the LangChain4j project has received 1,698 pull requests since the beginning of this year. Reviewing them all is a lot of work, and we wanted an agentic system to help. But a single pattern can't do it: routing, debating, voting and reflection all need to work together, within a cost budget, in a real Quarkus application. Here's how we built one that reviews a 2900-line pull request for $0.45. In previous articles we discussed why no single agentic pattern can cover all use cases, introducing a generic Planner abstraction to define custom orchestration strategies, and we showed how the voting pattern and dynamic chat model selection make an agentic system more reliable and more cost-efficient. Each of those articles focused on one pattern, applied to a deliberately small example. This time we want to see what happens when many of these patterns have to work together in a real application, with real costs, real failures, and a human who wants to have the last word. Given a pull request, the reviewer produces a report saying what is good, what is wrong and what could be improved, with every problem anchored to a file and a line of the diff. It also gives a score from 0 to 10 for usefulness, correctness, conciseness, security, test coverage, maintainability, API and documentation, and PR hygiene, plus an overall score with its confidence, and a verdict: APPROVE, COMMENT or REQUEST_CHANGES. It only reads GitHub, with a read-only token, and never writes to it: its output is a Markdown report, the same report in JSON, and an HTML trace of the execution of its agents. The reviewer is a Quarkus application built with the Quarkus LangChain4j extensions, version 1.15 on LangChain4j 1.21: quarkus-langchain4j-agentic for the agents, the Anthropic and OpenAI extensions for the chat models, quarkus-langchain4j-typesafe for the decision model (where TypeSafe is the company behind the Jev decision models), and quarkus-github-api to read GitHub. The

## Quarkus Insights #266: What's new in Leyden?

DevFeed: [Quarkus Insights #266: What's new in Leyden?](<https://devfeed.tech/articles/quarkus-insights-266-what-s-new-in-leyden-121114.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-insights-266-whats-new-in-leyden/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-11-02T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Project Leyden](<https://devfeed.tech/topics/project-leyden.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [openjdk](<https://devfeed.tech/topics/openjdk.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Instrumentation](<https://devfeed.tech/topics/instrumentation.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Project Valhalla](<https://devfeed.tech/topics/project-valhalla.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [aot](<https://devfeed.tech/tags/aot.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [beta](<https://devfeed.tech/tags/beta.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [c](<https://devfeed.tech/tags/c.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [cache](<https://devfeed.tech/tags/cache.md>), [code](<https://devfeed.tech/tags/code.md>), [compilation](<https://devfeed.tech/tags/compilation.md>), [conference](<https://devfeed.tech/tags/conference.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cummins](<https://devfeed.tech/tags/cummins.md>), [dev](<https://devfeed.tech/tags/dev.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [insights](<https://devfeed.tech/tags/insights.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

### AI overview

Project Leyden's AOT cache uses information collected in a training run to reduce Java startup warm-up, and JEP 544 (available from JDK 28) adds compiled native code to the cache. In Maria Arias de Reyna Dominguez's Quarkus tests, requests began around 20 ms with the cache versus 60 ms without it and reached peak performance after about 400 rather than 1,000 requests; the laptop results are illustrative, not server benchmarks. The JVM remains adaptive and recompiles code when production behavior differs from training. Using the cache requires predictable class loading; custom class loaders and agent-modified classes pose limitations. Production planning should account for larger images, CPU-specific code, pipeline changes, and training representative workloads through integration tests or canary traffic. Iterative training can refine caches from production use.

### Source excerpt

This summary was generated using AI, reviewed by humans - watch the video for the full story. Quarkus Insights #266: What's new in Leyden? Java gets faster the longer it runs, but what if an application could start out already warmed up? That is the goal of Project Leyden, and a lot has changed since Maria Arias de Reyna Dominguez last appeared on the show roughly a year ago. In episode 266, Maria, a committer on the OpenJDK project who works on Leyden at IBM, joins hosts Eric Deandrea and Holly Cummins to explain how the AOT cache works, what the newly merged ahead-of-time code compilation adds, what it takes to use the cache in production, and why the Leyden team wants feedback from real users now. Quarkus News Holly noted that the finish line for Quarkus 4 is in sight, and encouraged everyone to try Quarkus 4 Beta 2 if they have not already. The Quarkus:Dev conference call for papers is coming soon, so start thinking about the stories and projects you would like to share. A Quick Recap: Why Leyden Exists Project Leyden is one of several OpenJDK projects improving the Java language, the JVM, or the wider ecosystem, alongside efforts such as Project Valhalla. Leyden targets startup and warm-up time. Maria explained the underlying trade-off. A natively compiled C or C++ binary runs the same code from start to finish. Java instead ships bytecode that the JVM interprets, profiles, and recompiles repeatedly. Along the way it learns runtime-only facts, such as which branches are hot, which code is never used, and exactly which CPU instructions the hardware supports. That is why long-running Java applications can end up faster than ahead-of-time compiled code, but it also means the application is slowest right when it starts. Leyden's approach is a three-step workflow: Run the application in a training run to reach peak performance and collect runtime information. Store what was learned in an AOT cache. Start the real production run with the cache, so the JVM has that in

## Introducing the Quarkus Almanac

DevFeed: [Introducing the Quarkus Almanac](<https://devfeed.tech/articles/introducing-the-quarkus-almanac-107180.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-almanac/>)

Author: Fouad Almalki (https://twitter.com/engineer\_fouad)

Published: 2026-10-29T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [versioning](<https://devfeed.tech/topics/versioning.md>), [version-control](<https://devfeed.tech/topics/version-control.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [browser](<https://devfeed.tech/tags/browser.md>), [classes](<https://devfeed.tech/tags/classes.md>), [comparisons](<https://devfeed.tech/tags/comparisons.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [history](<https://devfeed.tech/tags/history.md>), [jackson](<https://devfeed.tech/tags/jackson.md>), [java](<https://devfeed.tech/tags/java.md>), [lts](<https://devfeed.tech/tags/lts.md>), [migration-guides](<https://devfeed.tech/tags/migration-guides.md>), [properties](<https://devfeed.tech/tags/properties.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [release-notes](<https://devfeed.tech/tags/release-notes.md>), [releases](<https://devfeed.tech/tags/releases.md>), [upgrades](<https://devfeed.tech/tags/upgrades.md>)

### AI overview

The Quarkus Almanac compares any two Quarkus releases, covering configuration properties, managed dependencies, extensions, and public or protected API changes. Comparisons summarize change counts and let users inspect relevant sections. Dependency comparisons use platform BOMs when both releases have them; users can switch to core BOMs, which may manage different versions. Release and history pages track changes across releases for properties, artifacts, and classes. The dataset is built from Quarkus artifacts published on Maven Central, updated every twelve hours by a GitHub workflow, and comparisons run in the browser on a static site.

### Source excerpt

Upgrading Quarkus starts with a question: what changed between the release I use and the one I want? The answer is spread over migration guides, release notes, the BOM, the configuration reference, and the code. The Quarkus Almanac puts it in one place. Pick two releases, and it shows what changed between them: config properties, managed dependencies, extensions, and the API of the classes in the Quarkus jars. It covers every Quarkus release, from 0.0.1 to the latest release. The Almanac is inspired by javaalmanac.io, the Java Version Almanac, which collects the history of every Java release and compares the API of any two of them. Compare two releases Pick a release to compare from and a release to compare to. The home page also offers quick comparisons, for example between two LTS releases. A comparison starts with a summary that counts the changes of each kind. The sections below it list the changes, and start collapsed: open the ones you need. Configuration The Configuration section lists the config properties that were added or removed, and those whose default value, type, accepted values, or phase changed, or that were deprecated. The properties are grouped by extension: open an extension to see its changes, or filter by property, extension, or description. Dependencies The Dependencies section compares the versions that the Quarkus BOM manages: major, minor, and patch upgrades, downgrades, and the artifacts that were added or removed. Applications generated by code.quarkus.io import the platform BOM, io.quarkus.platform:quarkus-bom, which sometimes manages other versions than the core BOM, io.quarkus:quarkus-bom. The Almanac compares the platform BOMs when both releases have one; turn off the Platform BOM switch to compare the core BOMs instead. From 3.33.3.3 to 3.33.4, for example, the platform BOM upgrades 68 Jackson artifacts from 2.21.6 to 2.21.7, while the core BOM keeps them at 2.21.6. Extensions The Extensions section lists the extensions that were add

## Quarkus Insights #265: Observability and Evaluation with Langfuse

DevFeed: [Quarkus Insights #265: Observability and Evaluation with Langfuse](<https://devfeed.tech/articles/quarkus-insights-265-observability-and-evaluation-with-langfuse-105774.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-insights-265-observability-and-evaluation-with-langfuse/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-10-26T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [observability](<https://devfeed.tech/topics/observability.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-applications](<https://devfeed.tech/tags/ai-applications.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [insights](<https://devfeed.tech/tags/insights.md>), [langchain4j](<https://devfeed.tech/tags/langchain4j.md>), [langfuse](<https://devfeed.tech/tags/langfuse.md>), [observability](<https://devfeed.tech/tags/observability.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>)

### AI overview

LLM applications can return fluent but incorrect answers while tests, health checks, and HTTP status codes all appear normal, so quality needs ongoing evaluation. The excerpt describes a Quarkus approach using LangChain4j, Langfuse, and OpenTelemetry: Quarkus Dev Services provisions Langfuse locally, and its extension forwards AI related spans to Langfuse while sending full traces to standard OpenTelemetry backends, with trace IDs preserved across both. Evaluation can score individual responses asynchronously, assess whole conversation sessions, and turn production datasets into CI checks that fail builds when scores fall below a configured threshold. The approach complements deterministic unit and resilience tests with qualitative checks, which add latency and compute cost. The excerpt also notes that the upstream Langfuse Java SDK's Jackson 2 and OkHttp dependencies conflict with Quarkus 4 needs, motivating a modular API using Quarkus REST capabilities.

### Source excerpt

This summary was generated using AI, reviewed by humans - watch the video for the full story. Quarkus Insights #265: Observability and Evaluation with Langfuse Traditional software testing relies on deterministic inputs and outputs: given the same arguments, a function should return the exact same result, and HTTP 200 responses signal that all systems are healthy. Large language models and generative AI break these assumptions by introducing non-determinism, where code can compile cleanly, tests pass, and operational dashboards glow green while the system produces completely incorrect or hallucinated answers. In episode 265, regular host Eric Deandrea swaps seats to become the featured guest, joining hosts Holly Cummins and Dimitris Andreadis to demonstrate how to bring observability, continuous evaluation, and regression testing to AI applications using Langfuse and LangChain4j. Quarkus News and Community Updates Holly opened the episode with notable updates from across the community: Quarkiverse release surge: A newly deployed release announcement automation recorded 27 new Quarkiverse extension releases in a single week. Quarkus 4 compatibility: Quarkiverse extension maintainers continue rolling out updates to ensure day-one compatibility with Quarkus 4. Quarkus:Dev conference announced: Following a community vote, the upcoming virtual conference has been named Quarkus:Dev and is scheduled for February 2nd to 3rd. Community members are encouraged to prepare story proposals and participate in the upcoming call for presentations. Time zone transitions: European daylight saving changes resulted in an hour shift between European and American broadcast schedules, giving Eric an extra hour to fine-tune his live demo. The Non-Deterministic Challenge: When Green Dashboards Hide Bad Answers In traditional enterprise architectures, components such as databases, message queues, and downstream microservices have well-understood failure modes. Engineers use unit tests, integr

## How Trax keeps aircraft maintenance real-time with Quarkus

DevFeed: [How Trax keeps aircraft maintenance real-time with Quarkus](<https://devfeed.tech/articles/how-trax-keeps-aircraft-maintenance-real-time-with-quarkus-101133.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/trax-real-time-aircraft-maintenance-with-quarkus/>)

Author: Emil Lefkof

Published: 2026-10-26T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [real-time](<https://devfeed.tech/topics/real-time.md>)

Tags: [aircraft](<https://devfeed.tech/tags/aircraft.md>), [airlines](<https://devfeed.tech/tags/airlines.md>), [batch](<https://devfeed.tech/tags/batch.md>), [changes](<https://devfeed.tech/tags/changes.md>), [control](<https://devfeed.tech/tags/control.md>), [controller](<https://devfeed.tech/tags/controller.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [desktop-application](<https://devfeed.tech/tags/desktop-application.md>), [erp](<https://devfeed.tech/tags/erp.md>), [event](<https://devfeed.tech/tags/event.md>), [flight](<https://devfeed.tech/tags/flight.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ipad](<https://devfeed.tech/tags/ipad.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [real-time](<https://devfeed.tech/tags/real-time.md>)

### AI overview

Trax's eMobility suite uses Quarkus to keep maintenance controllers' React dashboards and mechanics' iOS apps current while Oracle remains the shared system of record. Debezium reads Oracle redo logs and publishes changes to Kafka; Quarkus Kafka Streams handlers refresh caches and send compact invalidation messages over WebSockets, so clients re-fetch only affected data. Each pod uses its stable, unique HOSTNAME in the Kafka Streams application ID: separate consumer groups let every pod receive each event, while stability lets a restarted pod resume its group. Since CDC can emit many records for one action or batch, updates are coalesced by record identity and flushed after a shared one-second trailing delay. Foreground clients use WebSockets; backgrounded iPads receive APNs notifications. OpenAPI is generated and committed so Swift and React clients can be generated from one contract and catch API changes at build time. The account is an implementation overview; it does not report measured delivery latency or reliability.

### Source excerpt

Quarkus turns up in places most people never think to look for it. This one lives on the ramp, in the hangar, and in the hands of the mechanic standing under a wing at 3am. A short background on Trax Trax builds MRO software -- Maintenance, Repair and Overhaul -- for airlines, cargo operators and independent maintenance providers. If an aircraft is being worked on, something has to track it: the work orders, the task cards, the parts consumed, the sign-offs, the airworthiness records that a regulator can ask to see years later. Trax has been doing that for over 25 years, and today its systems cover thousands of aircraft for customers across dozens of countries. Historically this was a heavyweight desktop application backed by a very large Oracle database. The modern push is paperless maintenance: get the mechanic off the clipboard and onto an iPad at the aircraft, and give the maintenance controller a live web dashboard instead of a report that was true ten minutes ago. That product line is called eMobility, and the technology behind it is a suite of Quarkus applications. The problem These services have to serve two very different front ends: A React web application used by maintenance control and line control staff on desktops. A Swift/SwiftUI iOS application used by mechanics on iPads out at the aircraft. Both need the same data, and both need it to be current. When a work order changes status, when a flight's maintenance crew assignment moves, when a defect is raised against an aircraft, every connected client should know within seconds -- without hammering the database with polling. The wrinkle is that the system of record is the existing Oracle ERP database, and a great deal of what writes to it is not our service. Other Trax applications, batch jobs, and integrations all write to the same tables. We cannot simply fire an event from our own code after a transaction commits, because most of the interesting changes do not originate in our code at all. So the require

## AI Root Cause Analysis: Architecture, Testing, and Evaluation

DevFeed: [AI Root Cause Analysis: Architecture, Testing, and Evaluation](<https://devfeed.tech/articles/ai-root-cause-analysis-architecture-testing-and-evaluation-109738.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/ai-root-cause-analysis-deep-dive/>)

Author: Ales Justin

Published: 2026-10-23T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [ai observability](<https://devfeed.tech/topics/ai-observability.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [AI Architecture](<https://devfeed.tech/topics/ai-architecture.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [langchain4j](<https://devfeed.tech/topics/langchain4j.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Data visualization](<https://devfeed.tech/topics/data-visualization.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [chaos](<https://devfeed.tech/tags/chaos.md>), [chaos-engineering](<https://devfeed.tech/tags/chaos-engineering.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [langchain4j](<https://devfeed.tech/tags/langchain4j.md>), [lgtm](<https://devfeed.tech/tags/lgtm.md>), [llm](<https://devfeed.tech/tags/llm.md>), [llm-as-judge](<https://devfeed.tech/tags/llm-as-judge.md>), [logs](<https://devfeed.tech/tags/logs.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [no-code](<https://devfeed.tech/tags/no-code.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

AI Root Cause Analysis correlates traces, logs, and point-in-time Prometheus metrics through an LLM that autonomously selects telemetry tools and builds a structured report. OpenTelemetry-instrumented applications connect through an LGTM stack via MCP; optional Quarkus Dev MCP supports source examination and dashboard generation. A filtering layer strips SDK noise, redundant fields, and low-signal metrics (586 entries to about 35) to limit context use. Chaos tests inject application and network failures, including database and weather API faults via Toxiproxy, then score reports with a separate judge LLM on four dimensions (25 points each); the default passing threshold is 70/100 and can be overridden. Analyzer and scorer can use different providers to reduce self-evaluation bias. The excerpt reports 19 scenarios passing across provider combinations.

### Source excerpt

In the introductory post, we showed what AI Root Cause Analysis does and how to get started. This post goes deeper -- into the architecture, the analysis pipeline, how we keep telemetry data within LLM context limits, and how we test analysis quality using chaos engineering with LLM-as-judge evaluation. Architecture The system has a layered architecture connecting monitored applications to the AI analysis engine through an observability stack: Your applications just need OpenTelemetry instrumentation -- no code changes required. The AI module connects to your existing LGTM stack via MCP and optionally to your running Quarkus applications via Quarkus Dev MCP for source examination and dashboard generation. The AI module uses LangChain4j @RegisterAiService interfaces backed by a ~290-line system prompt that instructs the LLM on three-way telemetry correlation, chaos detection patterns, severity classification, and structured output formatting. Five tools are exposed to the LLM during analysis: Tool What It Provides provideLastNTraceIds Recent trace IDs from Tempo (TraceQL) traceById Full trace data for a specific trace logsWithTraceId Correlated Loki logs for a trace getRootSpanStartTime Timestamp for metric queries getAllMetricsForDatetime Prometheus metrics at a point in time The LLM orchestrates these tools autonomously -- it decides which traces look interesting, pulls their logs, checks metrics, and builds the analysis iteratively. The Analysis Pipeline When you hit GET /analyze/{n}, the following sequence unfolds: Tool dispatch -- The AI module sends the system prompt and tool definitions to the LLM Trace retrieval -- The LLM calls provideLastNTraceIds to get the N most recent traces Per-trace investigation -- For each trace, the LLM pulls full trace data and correlated logs through StripMcpClient, which strips SDK noise, localhost attributes, and redundant fields Metrics context -- The LLM queries Prometheus metrics at the root span's start time; the filtering layer r

## Extending Your Quarkus Application with Apache Camel

DevFeed: [Extending Your Quarkus Application with Apache Camel](<https://devfeed.tech/articles/extending-your-quarkus-application-with-apache-camel-113383.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/extending-quarkus-with-camel/>)

Author: Gaelle Fournier

Published: 2026-10-23T00:00:00Z

Content type: tutorial

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [apache-camel](<https://devfeed.tech/tags/apache-camel.md>), [api](<https://devfeed.tech/tags/api.md>), [csv](<https://devfeed.tech/tags/csv.md>), [file](<https://devfeed.tech/tags/file.md>), [integration](<https://devfeed.tech/tags/integration.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [rest-api](<https://devfeed.tech/tags/rest-api.md>)

### AI overview

The excerpt shows how to extend a Quarkus order API with Camel Quarkus routes for three integration tasks: publish orders as JSON to Kafka, notify a loyalty API over HTTP with up to three retries using exponential backoff, and ingest CSV files into the existing repository while moving processed and failed files to separate directories. A `ProducerTemplate` call connects the existing REST endpoint to the Kafka and HTTP route; CSV ingestion runs in a separate file route. The example notes the retry policy applies to Kafka steps too, and exhausted retries are logged and handled while the order remains persisted. It presents Camel's shared route model as useful as integrations grow, while stating that Quarkus Reactive Messaging is enough for a single Kafka topic.

### Source excerpt

Introduction You built a standard Quarkus application: REST endpoints, a service layer, a database. Then you are given a new requirement: "When an order is placed, send an event to Kafka so the analytics team can track it." A week later another one: "Also notify the partner loyalty system via their REST API and make sure to handle it properly when their API is down." And another one: "The partner is going to start sending us CSV order files."... Each of these requirements is an integration task, and Quarkus already gives you building blocks for all of them: Reactive Messaging for Kafka, the REST client with fault tolerance for the loyalty API, a scheduled job for file polling. But you could also hand all three to Apache Camel, which covers them with a single model. Retry with backoff, error policies, JSON and CSV conversion, file polling that moves handled files aside: each one is a built-in step you declare on a route, a line at a time, in the same vocabulary whichever system you are talking to. And it runs inside the application you already have. Camel Quarkus packages over 300 of Camel's components as Quarkus extensions, as natural to use as any other CDI bean. In this post we start from a working Quarkus REST application and progressively extend it with three integration capabilities using Camel. You'll see exactly what changes in your existing code and what stays untouched. The starting point Here's what we're starting with: a simple order management REST API. @Path("/api/orders") @Produces(MediaType.APPLICATION_JSON) @Consumes(MediaType.APPLICATION_JSON) public class OrderResource { @Inject OrderRepository repository; @GET public List<Order> list() { return repository.listAll(); } @POST public Response create(Order order) { repository.add(order); return Response.status(Response.Status.CREATED).entity(order).build(); } } Order is a POJO with four fields (id, customer, type, amount), a no-arg constructor and an all-args one. OrderRepository is an @ApplicationScop

## AI Root Cause Analysis: LLM-Powered Root-Cause Analysis for Distributed Systems

DevFeed: [AI Root Cause Analysis: LLM-Powered Root-Cause Analysis for Distributed Systems](<https://devfeed.tech/articles/ai-root-cause-analysis-llm-powered-root-cause-analysis-for-distributed-systems-109739.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/ai-root-cause-analysis/>)

Author: Ales Justin

Published: 2026-10-22T00:00:00Z

Content type: tutorial

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [bridges](<https://devfeed.tech/tags/bridges.md>), [but](<https://devfeed.tech/tags/but.md>), [cause](<https://devfeed.tech/tags/cause.md>), [complete](<https://devfeed.tech/tags/complete.md>), [context](<https://devfeed.tech/tags/context.md>), [details](<https://devfeed.tech/tags/details.md>), [developers](<https://devfeed.tech/tags/developers.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-system](<https://devfeed.tech/tags/distributed-system.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [don-t](<https://devfeed.tech/tags/don-t.md>), [llm](<https://devfeed.tech/tags/llm.md>), [root](<https://devfeed.tech/tags/root.md>), [root-cause-analysis](<https://devfeed.tech/tags/root-cause-analysis.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

AI Root Cause Analysis is an open-source Quarkus application that uses MCP to gather traces from Tempo, correlated logs from Loki, and time-matched metrics from Prometheus, then asks an LLM to produce structured findings on root causes, severity, cascading failures, and remediation. A StripMcpClient filters telemetry noise before it reaches the model; the source reports reducing one metrics set from 586 entries to about 35. Optional Quarkus Dev MCP integration lets it examine application code and write generated Grafana dashboards into app workspaces. Without that integration, core telemetry analysis still works, but source examination is disabled and dashboards must be copied from the UI and imported manually. The excerpt lists OpenAI (default), Grok, Gemini, and WatsonX profiles; Anthropic and native-image support are described as future priorities.

### Source excerpt

When something goes wrong in a distributed system, engineers face the same ritual: open Grafana, dig through traces in Tempo, correlate logs in Loki, check Prometheus metrics, and mentally piece together a causal chain across services. What if an LLM could do that for you -- pulling telemetry from the same tools you already use and producing a structured root-cause analysis in seconds? That's what AI Root Cause Analysis does. It's an open-source Quarkus application that connects to your existing Grafana LGTM stack via MCP (Model Context Protocol), feeds correlated traces, logs, and metrics to an LLM, and returns actionable analysis -- complete with root causes, severity assessments, and remediation suggestions. Who Is This For? AI Root Cause Analysis is built for developers who work with distributed systems but don't want to become observability experts. You know your LGTM stack is collecting traces, logs, and metrics -- but correlating them across services, spotting the root cause in a wall of spans, and distinguishing symptoms from causes takes experience and time. The AI handles that for you: it knows how to query Tempo, Loki, and Prometheus, understands what the telemetry means in context, and draws correlations that would take manual investigation to piece together. If you're comfortable with AI but not with the details of trace propagation, span hierarchies, or PromQL -- this tool bridges that gap. What It Does AI Root Cause Analysis is a standalone analysis engine. Point it at your LGTM stack and your running applications, and it will: Retrieve recent traces from Tempo via MCP and identify the interesting ones (errors, high latency, unusual patterns) Correlate logs for each trace from Loki, linking log entries to specific spans Pull Prometheus metrics at the time window of each trace to add system-level context Analyze everything together using an LLM, producing a structured report that distinguishes root causes from symptoms, identifies cascading failures, and s

## Quarkus 3.33.4.1 released - LTS emergency release

DevFeed: [Quarkus 3.33.4.1 released - LTS emergency release](<https://devfeed.tech/articles/quarkus-3-33-4-1-released-lts-emergency-release-90801.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-3-33-4-1-released/>)

Author: Jan Martiška (https://twitter.com/janmartiska)

Published: 2026-10-19T00:00:00Z

Content type: release

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Release notes](<https://devfeed.tech/topics/release-notes.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [community](<https://devfeed.tech/tags/community.md>), [cves](<https://devfeed.tech/tags/cves.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [lts](<https://devfeed.tech/tags/lts.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [release](<https://devfeed.tech/tags/release.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

Quarkus 3.33.4.1 is an emergency release for the 3.33 LTS stream. It fixes CVE-2026-93879, CVE-2026-94451, and CVE-2026-87744, along with issues resolved in Jackson 2.21.7, snappy-java 1.1.10.11, lz4-java 1.11.4, Netty 4.1.139.Final, and Vert.x 4.5.35. The announcement says the corresponding Netty CVEs were not yet published at release time and describes the upgrade as safe for users already on 3.33. To update, use the latest Quarkus CLI and run `quarkus update --stream=3.33`; the command can also update applications from earlier Quarkus versions, including 2.x.

### Source excerpt

Today, we released Quarkus 3.33.4.1, an emergency release for the 3.33 LTS stream. This release fixes the following CVEs: CVE-2026-93879 CVE-2026-94451 CVE-2026-87744 Everything resolved by Jackson 2.21.7 Everything resolved by snappy-java 1.1.10.11 Everything resolved by lz4-java 1.11.4 Everything resolved by Netty 4.1.139.Final (note that, at the time of publishing this announcement, the corresponding CVEs have not been published yet) Everything resolved by Vert.x 4.5.35 It should be a safe upgrade for anyone already using 3.33. Update To update to Quarkus 3.33, we recommend updating to the latest version of the Quarkus CLI and run: quarkus update --stream=3.33 Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.33. Full changelog You can get the full changelog of 3.33.4.1 on GitHub. Come Join Us We value your feedback a lot so please report bugs, ask for improvements... Let's build something great together! If you are a Quarkus user or just curious, don't be shy and join our welcoming community: provide feedback on GitHub; craft some code and push a PR; discuss with us on Zulip and on the mailing list; ask your questions on Stack Overflow.

## Quarkus 3.27.6.1 released - LTS emergency release

DevFeed: [Quarkus 3.27.6.1 released - LTS emergency release](<https://devfeed.tech/articles/quarkus-3-27-6-1-released-lts-emergency-release-90800.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-3-27-6-1-released/>)

Author: Jan Martiška (https://twitter.com/janmartiska)

Published: 2026-10-19T00:00:00Z

Content type: release

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [Release notes](<https://devfeed.tech/topics/release-notes.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [changelog](<https://devfeed.tech/tags/changelog.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cves](<https://devfeed.tech/tags/cves.md>), [github](<https://devfeed.tech/tags/github.md>), [jackson](<https://devfeed.tech/tags/jackson.md>), [lts](<https://devfeed.tech/tags/lts.md>), [lz4](<https://devfeed.tech/tags/lz4.md>), [pr](<https://devfeed.tech/tags/pr.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [release](<https://devfeed.tech/tags/release.md>), [stack-overflow](<https://devfeed.tech/tags/stack-overflow.md>), [stream](<https://devfeed.tech/tags/stream.md>), [update](<https://devfeed.tech/tags/update.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [using](<https://devfeed.tech/tags/using.md>)

### AI overview

Quarkus 3.27.6.1 is an emergency release for the 3.27 LTS stream. It fixes three listed CVEs and includes resolutions from Jackson 2.21.7, snappy-java 1.1.10.11, lz4-java 1.11.4, Netty 4.1.139.Final, and Vert.x 4.5.35; the announcement says Netty's corresponding CVEs were not yet published. The release is described as a safe upgrade for users already on 3.27. To update, use the latest Quarkus CLI and run `quarkus update --stream=3.27`; the command can update applications from other Quarkus versions, including 2.x.

### Source excerpt

Today, we released Quarkus 3.27.6.1, an emergency release for the 3.27 LTS stream. This release fixes the following CVEs: CVE-2026-93879 CVE-2026-94451 CVE-2026-87744 Everything resolved by Jackson 2.21.7 Everything resolved by snappy-java 1.1.10.11 Everything resolved by lz4-java 1.11.4 Everything resolved by Netty 4.1.139.Final (note that, at the time of publishing this announcement, the corresponding CVEs have not been published yet) Everything resolved by Vert.x 4.5.35 It should be a safe upgrade for anyone already using 3.27. Update To update to Quarkus 3.27, we recommend updating to the latest version of the Quarkus CLI and run: quarkus update --stream=3.27 Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.27. Full changelog You can get the full changelog of 3.27.6.1 on GitHub. Come Join Us We value your feedback a lot so please report bugs, ask for improvements... Let's build something great together! If you are a Quarkus user or just curious, don't be shy and join our welcoming community: provide feedback on GitHub; craft some code and push a PR; discuss with us on Zulip and on the mailing list; ask your questions on Stack Overflow.

## Quarkus 3.40.1.1 released - LTS emergency release

DevFeed: [Quarkus 3.40.1.1 released - LTS emergency release](<https://devfeed.tech/articles/quarkus-3-40-1-1-released-lts-emergency-release-90802.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-3-40-1-1-released/>)

Author: Jan Martiška (https://twitter.com/janmartiska)

Published: 2026-10-19T00:00:00Z

Content type: release

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [Release notes](<https://devfeed.tech/topics/release-notes.md>)

Tags: [community](<https://devfeed.tech/tags/community.md>), [cves](<https://devfeed.tech/tags/cves.md>), [lts](<https://devfeed.tech/tags/lts.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [release](<https://devfeed.tech/tags/release.md>)

### AI overview

Quarkus 3.40.1.1 is an emergency release for the 3.40 LTS stream. It fixes CVE-2026-93879, CVE-2026-94451, and CVE-2026-87744, plus issues resolved in snappy-java 1.1.10.11, lz4-java 1.11.4, Netty 4.1.139.Final, and Vert.x 4.5.35. The announcement says related Netty CVEs had not yet been published when it was written and describes the upgrade as safe for users already on 3.40. To update, it recommends the latest Quarkus CLI and `quarkus update --stream=3.40`; the command can also migrate applications from earlier versions, including 2.x.

### Source excerpt

Today, we released Quarkus 3.40.1.1, an emergency release for the 3.40 LTS stream. This release fixes the following CVEs: CVE-2026-93879 CVE-2026-94451 CVE-2026-87744 Everything resolved by snappy-java 1.1.10.11 Everything resolved by lz4-java 1.11.4 Everything resolved by Netty 4.1.139.Final (note that, at the time of publishing this announcement, the corresponding CVEs have not been published yet) Everything resolved by Vert.x 4.5.35 It should be a safe upgrade for anyone already using 3.40. Update To update to Quarkus 3.40, we recommend updating to the latest version of the Quarkus CLI and run: quarkus update --stream=3.40 Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.40. Full changelog You can get the full changelog of 3.40.1.1 on GitHub. Come Join Us We value your feedback a lot so please report bugs, ask for improvements... Let's build something great together! If you are a Quarkus user or just curious, don't be shy and join our welcoming community: provide feedback on GitHub; craft some code and push a PR; discuss with us on Zulip and on the mailing list; ask your questions on Stack Overflow.

## Quarkus Insights #264: JobRunr 9 on Quarkus 3.40 LTS: What Happens When a Job Fails Halfway?

DevFeed: [Quarkus Insights #264: JobRunr 9 on Quarkus 3.40 LTS: What Happens When a Job Fails Halfway?](<https://devfeed.tech/articles/quarkus-insights-264-jobrunr-9-on-quarkus-3-40-lts-what-happens-when-a-job-fails-halfway-93904.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-insights-264-jobrunr-failure-handling/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-10-19T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Job](<https://devfeed.tech/topics/job.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [clean energy data centers](<https://devfeed.tech/topics/clean-energy-data-centers.md>)

Tags: [background-job-processing](<https://devfeed.tech/tags/background-job-processing.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [jobrunr](<https://devfeed.tech/tags/jobrunr.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [retry](<https://devfeed.tech/tags/retry.md>)

### AI overview

JobRunr 9 pairs with Quarkus 3.40 LTS to run Java background work asynchronously: services enqueue lambdas, jobs are persisted in a shared database, and separate workers poll and execute them. Its Quarkus extension exposes `JobScheduler` through CDI. For partial failures, `JobContext.runStepOnce(...)` records successful steps so retries skip them and resume at the failed step, reducing the risk of repeating side effects; the dashboard shows step status and execution timelines. Carbon-aware scheduling uses ENTSO-E forecasts in Europe and Electricity Maps in North America, with jobs deferred to the end of the requested window if forecasting APIs are unavailable. The text says Open Source includes retries, carbon-aware scheduling, and a dashboard; Pro adds features such as priority queues, multi-tenancy, job chaining, and approval workflows.

### Source excerpt

This summary was generated using AI, reviewed by humans - watch the video for the full story. Quarkus Insights #264: JobRunr 9 on Quarkus 3.40 LTS: What Happens When a Job Fails Halfway? Background job processing is essential for modern web applications, yet handling long-running distributed tasks reliably remains a persistent challenge. What happens when a multi-step job bills a customer, generates an invoice, and crashes while sending an email? In episode 264, Ronald Dehuysser, creator and founder of JobRunr, joins hosts Eric Deandrea and Holly Cummins to celebrate the release of JobRunr 9 and its day-one alignment with Quarkus 3.40 LTS. Through live coding and architectural discussion, Ronald demonstrates how JobRunr simplifies distributed processing in Java, schedules background tasks around clean energy grid forecasts, and guarantees step-level idempotency so failed jobs can safely retry without duplicating side effects. Quarkus Ecosystem News Holly kicked off the episode with updates across the Quarkus ecosystem: Quarkus 3.40.1.1: A fresh micro release is available on the latest long-term support (LTS) stream. Ecosystem releases for Quarkus 4 beta: With the Quarkus 4 beta available, numerous Quarkiverse and ecosystem projects have published new releases, many providing early compatibility: Quarkus GitHub Actions 3.0.0 beta 2 JasperReports 1.4.2 Quarkus Amazon Web Services (AWS) 4.0.0 beta 3 Quarkus Temporal 1.0 Quarkus Network Faults 0.2.0 (designed for chaos engineering and failure injection SystemD Notify 1.1 (integrating with systemd service notifications) IronJacamar 2.0 beta 2 Quarkus PrimeFaces 4.16.1 Quinoa 2.9.3 Roq 1.2.20 Origins and Architecture of JobRunr Ronald shared the backstory behind JobRunr. While freelancing prior to the pandemic, he faced distributed computing challenges in Java where background tasks lacked consistent correlation IDs, jobs vanished into dead-letter queues without monitoring, and debugging required parsing disjointed logs.

## Quarkus Newsletter #73 - October

DevFeed: [Quarkus Newsletter #73 - October](<https://devfeed.tech/articles/quarkus-newsletter-73-october-88258.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-newsletter-73/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-10-15T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>)

Tags: [chaos-engineering](<https://devfeed.tech/tags/chaos-engineering.md>), [jobrunr](<https://devfeed.tech/tags/jobrunr.md>), [newsletter](<https://devfeed.tech/tags/newsletter.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>)

### AI overview

Quarkus Newsletter #73 highlights articles on an IBM Bob ACP local control plane, JobRunr v9 background job monitoring and analytics, the migration of quarkus.io to Quarkus Roq, desktop applications with Quarkus, and a hands-on chaos engineering example using a quote API.

### Source excerpt

Check out "IBM Bob ACP in Quarkus: A Local Control Plane, Not a Shared Chat App" by Markus Eisele to how permission futures, workspace bounds, and loopback binding show why this client stays on one machine until you add auth, quotas, and audit. JobRunr v9 draws every attempt and every durable step of a job on a chart. JobRunr Pro v9 adds Job Analytics to the dashboard, can pause and resume a batch halfway and starts jobs within milliseconds on Postgres, without multicast. Get the details in "JobRunr & JobRunr Pro v9: See Inside Every Background Job" by the JobRunr Team. The quarkus.io site is now built with Quarkus Roq. Read Holly Cummins's blog post to learn how we migrated quarkus.io from Jekyll to Quarkus Roq by converting 40,000 files, delivering faster builds, quicker page loads, and simplified Java-based local development. Fouad Almalki's "Build AWT and Swing desktop applications with Quarkus Desktop" shows how Quarkus Desktop brings AWT and Swing applications to Quarkus, in JVM mode and as native executables on Windows, Linux, and macOS. Read "Quarkus Goblin: Learn Chaos Engineering on One REST Call" by Markus Eisele to learn how to build a quote API that calls inventory, inject latency and HTTP 503s, and watch timeout, retry, and fallback take over. You will also see the latest Quarkus Insights episodes, top social posts and upcoming Quarkus attended events. Check out Newsletter #73: October! Want to get newsletters in your inbox? Sign up for the newsletter using the on page form.

## Quarkus builds: challenges and safeguards for reproducibility

DevFeed: [Quarkus builds: challenges and safeguards for reproducibility](<https://devfeed.tech/articles/quarkus-insights-263-everything-you-didn-t-want-to-know-about-quarkus-build-reproducibility-87684.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-insights-263-quarkus-build-reproducibility/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-10-12T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [Maven](<https://devfeed.tech/topics/maven.md>)

Tags: [build-tool](<https://devfeed.tech/tags/build-tool.md>), [bytecode](<https://devfeed.tech/tags/bytecode.md>), [development](<https://devfeed.tech/tags/development.md>), [java](<https://devfeed.tech/tags/java.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [reproducibility](<https://devfeed.tech/tags/reproducibility.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>)

### AI overview

Quarkus Insights episode 263 examines why bit-for-bit reproducible builds are difficult in Quarkus, where ahead-of-time bytecode generation and parallel build steps introduce sources of nondeterminism. The team describes fixes for ordering, shared counters, collections and composite indexing, alongside multi-tiered checks and nightly CI verification. They also discuss using diffoscope and LLMs to categorize failures, with engineers making the architectural decisions.

### Source excerpt

This summary was generated using AI, reviewed by humans - watch the video for the full story. Quarkus Insights # 263: Everything You Didn't Want to Know About Quarkus Build Reproducibility Achieving reproducible builds in modern software is often described as straightforward: pin your dependencies, use a deterministic compiler, and let your build tool do the rest. In a framework like Quarkus, however, where the build process performs heavy ahead-of-time bytecode generation and executes build steps across multiple parallel threads, determinism is anything but simple. In episode 263, community contributor Teymur (Tim) Babayev and Quarkus core maintainers Guillaume Smet and Ladislav Thon join host Holly Cummins to unpack the technical challenges of making Quarkus builds bit-for-bit reproducible, the insidious sources of non-determinism they uncovered, and the infrastructure now in place to ensure our binaries continue to stay reproducible. Quarkus News Holly opened the episode with an unusual announcement: for the first time in months, there was no new minor or micro release during the week. With the release cadence briefly paused, Guillaume took a well-earned break from preparing backports. The core team is currently focused on iterating on the Quarkus 4 betas leading up to the final release, with micro releases on earlier streams reserved strictly for critical CVEs. Community members are encouraged to try out the Quarkus 4 beta, test their applications, and report any issues or feedback. What Is Build Reproducibility and Why Does It Matter? Guillaume kicked off the technical discussion by defining build reproducibility according to the principles of Reproducible Builds: given the exact same source code, same Java Development Kit (JDK), same operating system, and identical build inputs, the build must produce the exact same binary output bit-for-bit. Two major requirements drive the need for reproducible builds: Supply chain security and forensics: High-profile securi

## Quarkus Insights #262: What is Quarkus Chat Scopes?

DevFeed: [Quarkus Insights #262: What is Quarkus Chat Scopes?](<https://devfeed.tech/articles/quarkus-insights-262-what-is-quarkus-chat-scopes-85898.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-insights-262-quarkus-chat-scopes/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-10-05T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [langchain4j](<https://devfeed.tech/topics/langchain4j.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [langchain4j](<https://devfeed.tech/tags/langchain4j.md>), [llm](<https://devfeed.tech/tags/llm.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>)

### AI overview

This Quarkus Insights episode presents Quarkus Chat Scopes, a CDI conversational scope and WebSocket-based framework for building multi-turn LLM chat applications. It covers conversation state and memory management, nested workflows, remote chat routes, and Java and JavaScript clients.

### Source excerpt

This summary was generated using AI, reviewed by humans - watch the video for the full story. Quarkus Insights #262: What is Quarkus Chat Scopes? Building a chat UI backed by an LLM sounds straightforward until you try to hold a real multi-turn conversation on a server that only knows about request scope and application scope. In episode 262, Bill Burke, a longtime Red Hat/IBM architect, EJB specification veteran, author of O'Reilly books on RESTful Java, and contributor to Quarkus Lambda and Azure Functions integrations, joins hosts Eric Deandrea and Holly Cummins to present the solution he built: Quarkus Chat Scopes, a new CDI conversational scope and client-server remoting framework living inside Quarkus LangChain4j. Quarkus News Holly opened with a notable week of releases. The long-awaited Quarkus 4 beta is now available for anyone who wants to kick the tires. Quarkus 3.40, the last LTS on the 3.x stream, is also out and ready for teams looking to move to the latest long-term support baseline. For those who prefer in-person feedback, several members of the Quarkus team will be at Devoxx Belgium, and Eric will be at dev2next in Denver, Colorado the following week for anyone who cannot make it to Europe. The Problem: Chat Applications Need More Than Request Scope Bill's framing is rooted in direct experience. A year and a half ago he started writing chat applications with Quarkus LangChain4j and quickly ran into three gaps: No conversation-scoped state. LLM conversations are managed on the server, but beyond chat memory, applications need to store and reference intermediate business state across multiple user messages. The built-in @RequestScoped and @ApplicationScoped CDI scopes are the wrong shape: request scope destroys everything when the response returns, and application scope is global. No structured memory ID management. Without a first-class conversation scope, developers had to manually pass @MemoryId-annotated parameters throughout their AI services to

## Quarkus 4.0.0.Beta1 released

DevFeed: [Quarkus 4.0.0.Beta1 released](<https://devfeed.tech/articles/quarkus-4-0-0-beta1-released-63157.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-4-0-0-beta1-released/>)

Author: Guillaume Smet (https://twitter.com/gsmet\_)

Published: 2026-10-01T00:00:00Z

Content type: release

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [WebSocket](<https://devfeed.tech/topics/websocket.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>)

Tags: [beta](<https://devfeed.tech/tags/beta.md>), [hibernate-orm](<https://devfeed.tech/tags/hibernate-orm.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [io-uring](<https://devfeed.tech/tags/io-uring.md>), [jackson](<https://devfeed.tech/tags/jackson.md>), [java](<https://devfeed.tech/tags/java.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [quic](<https://devfeed.tech/tags/quic.md>), [release](<https://devfeed.tech/tags/release.md>)

### AI overview

Quarkus 4.0.0.Beta1 is the first beta of the next major Quarkus version, with a final release planned for the end of November. The release highlights Java 21, updated networking components, optional HTTP/3 and QUIC support, observability features, and major upgrades to Jakarta REST, Hibernate ORM, Jackson, and CDI. Extension developers are asked to migrate their extensions, and users are encouraged to test their applications and report issues.

### Source excerpt

It is our pleasure to announce the availability of Quarkus 4.0.0.Beta1, the first Beta of the next major version of Quarkus. Quarkus 4 is a major new version and comes with a lot of changes. The final release is planned for the end of November. We need extension developers to migrate their extensions and end users to test their applications with it. Your feedback at this stage is essential to make Quarkus 4 a great release, please report any issues you encounter on GitHub. Highlights Quarkus 4 comes with significant upgrades across the board, and more are coming: Java 21 New base Java version, making virtual threads more central. Netty 4.2 and Vert.x 5.x New foundation for the networking layer. QUIC support QUIC is becoming the new foundation of distributed systems: HTTP/3, MQTT over QUIC, WebTransport (WebSocket over QUIC)... HTTP/3 Opt-in support for HTTP/3 with automatic certificate generation in dev and test modes. Native transports Improve the concurrency of your application with epoll or io_uring support. Also works in native executables. Observation API @Observed or programmatic API to generate metrics and traces. Works with Micrometer and OpenTelemetry. Dev UI Observability dashboard Built-in Observability section in the Dev UI, available out of the box in dev mode with no wiring needed. Jakarta REST 4 JSON Merge Patch, new multipart API. Hibernate ORM 8 Integration of the new major version of Hibernate with Jakarta Persistence 4.0 and Jakarta Data 1.1. Jackson 3 New major version - everything has changed except for the annotations. CDI 5.0 New annotations such as @Reserve and @Eager. New JMS extension Dedicated JMS extension with compatibility with Spring JMS, pooled JMS, and IronJacamar. @ExactlyOnce Improved Kafka transaction support. Upgrading to Quarkus 4 Migration guide We wrote a migration guide. As expected for a new major version, it is more dense than for our usual minors. For extension developers If you are maintaining a Quarkus extension, now is t

## Build AWT and Swing desktop applications with Quarkus Desktop

DevFeed: [Build AWT and Swing desktop applications with Quarkus Desktop](<https://devfeed.tech/articles/build-awt-and-swing-desktop-applications-with-quarkus-desktop-62158.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-desktop/>)

Author: Fouad Almalki (https://twitter.com/engineer\_fouad)

Published: 2026-09-30T00:00:00Z

Content type: tutorial

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Swing](<https://devfeed.tech/topics/swing.md>), [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Electron](<https://devfeed.tech/topics/electron.md>), [Maven](<https://devfeed.tech/topics/maven.md>)

Tags: [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [graalvm](<https://devfeed.tech/tags/graalvm.md>), [java](<https://devfeed.tech/tags/java.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [run](<https://devfeed.tech/tags/run.md>)

### AI overview

Quarkus Desktop lets Java teams build AWT and Swing applications as GraalVM native executables. The extension registers the platform resources these applications need, supports JVM, development, and native modes across Windows, Linux, and macOS, and integrates windows and desktop events with Quarkus CDI. The article also explains event dispatch thread rules and handling macOS application menu events.

### Source excerpt

Java has shipped AWT and Swing for decades, and many teams still build and maintain desktop applications with them. A GraalVM native executable is attractive for these applications: it starts fast, needs no JVM on the user's machine, and ships as one executable with a few libraries. But AWT and Swing are hard to compile natively. The JDK looks up classes, resources, and JNI callbacks by name, and each platform uses its own set. Quarkus Desktop is a Quarkus extension for these applications. It registers what AWT, Java2D, fonts, images, printing, the clipboard, drag and drop, input methods, sound, accessibility, and Swing need in a native executable. It also copies the JDK libraries that the executable loads next to it. The same application runs in JVM mode, in dev mode, and as a native executable on Windows, Linux, and macOS. Add the extension Add Quarkus Desktop Swing to your application: <dependency> <groupId>io.quarkiverse.desktop</groupId> <artifactId>quarkus-desktop-swing</artifactId> <version>0.1.0</version> </dependency> For an application that only uses AWT, add quarkus-desktop-awt instead. You can find the latest version on Maven Central. Open a window With Quarkus Desktop, a window is a CDI bean. It observes DesktopStartupEvent, which is fired on the event dispatch thread once the application has started: import io.quarkiverse.desktop.awt.DesktopStartupEvent; @Singleton public class MainWindow extends JFrame { @Inject Library library; @ConfigProperty(name = "app.title", defaultValue = "Library") String title; void open(@Observes DesktopStartupEvent event) { setTitle(title); setDefaultCloseOperation(DISPOSE_ON_CLOSE); add(new JScrollPane(new JList<>(library.titles()))); pack(); setVisible(true); } } The window gets @Inject and @ConfigProperty like any other bean. There is no main method and no @QuarkusMain. When the last window is closed, the application exits through Quarkus, so ShutdownEvent observers and @PreDestroy methods run. Windows are @Singleton or

## Quarkus 3.27.6 released - LTS maintenance release

DevFeed: [Quarkus 3.27.6 released - LTS maintenance release](<https://devfeed.tech/articles/quarkus-3-27-6-released-lts-maintenance-release-63155.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-3-27-6-released/>)

Author: Jan Martiška (https://twitter.com/janmartiska)

Published: 2026-09-30T00:00:00Z

Content type: release

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Release notes](<https://devfeed.tech/topics/release-notes.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [bugfixes](<https://devfeed.tech/tags/bugfixes.md>), [jackson](<https://devfeed.tech/tags/jackson.md>), [lts](<https://devfeed.tech/tags/lts.md>), [mariadb](<https://devfeed.tech/tags/mariadb.md>), [release](<https://devfeed.tech/tags/release.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Quarkus 3.27.6 is a maintenance release for the 3.27 LTS stream with bug fixes, documentation updates, and security fixes. It is planned as the final 3.27 update; users are advised to consider upgrading to 3.33 or 3.40. The release also provides a Quarkus CLI command for updating applications.

### Source excerpt

Today, we released Quarkus 3.27.6, our next maintenance release for the 3.27 LTS stream. This release contains bugfixes, documentation updates, and security fixes. It should be a safe upgrade for anyone already using 3.27. Please note that this is planned to be the last update to 3.27. Anybody still on 3.27 is advised to look into upgrading to 3.33 or 3.40 (the next LTS) soon. Security fixes This release fixes the following CVEs: Quarkus and direct dependencies CVE-2026-89407 - FasterXML jackson-core: Denial of Service via quadratic regex backtracking in number validation CVE-2026-89425 - FasterXML jackson-core: Denial of Service via unbounded error-token accumulation in UTF8DataInputJsonParser CVE-2026-91777 - FasterXML jackson-databind: Denial of Service via quadratic-time forward-reference resolution for @JsonIdentityInfo CVE-2026-91776 - FasterXML jackson-databind: Denial of Service via unbounded deserializer cache growth for unrecognized polymorphic type IDs CVE-2026-84939 - Apache FreeMarker: Path traversal via malformed locale identifier CVE-2026-94449 - Quarkus SmallRye Fault Tolerance: Memory leak in @ApplyGuard leads to Denial of Service CVE-2026-82617 - Apache OpenNLP: Denial of Service via super-linear regex backtracking in built-in name finders CVE-2026-68497 - Jackson-databind: Denial of Service via unbounded number parsing for Duration/XMLGregorianCalendar CVE-2026-89059 - RESTEasy: Denial of Service via unbounded memory allocation in IIOImageProvider CVE-2026-93432 - Quarkus Qute: Cross-Site Scripting via missing content-type propagation in {#eval} sub-templates CVE-2026-59949 - LZ4 Java: Denial of Service via native XXHash crash on invalid byte array ranges CVE-2026-61700 - MariaDB Connector/J: allowLocalInfile=false bypass via server-initiated LOCAL INFILE request CVE-2026-55856 - MariaDB Connector/J: Cleartext password disclosure via MITM on the initial handshake CVE-2026-55857 - MariaDB Connector/J: Cleartext transmission of credentials during PA

[Next page](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md?cursor=WyIyMDI2LTA5LTMwVDAwOjAwOjAwKzAwOjAwIiwgImNhNzk4NzBhLTQwMTctNDgzZS04ZDE5LTkwMDBhNmRjMjc1NyJd>)