Well, first, be prepared to downgrade your GraalVM installation to 19.2.1 for the upcoming 1.1.0.Final.

We are full steam to bring GraalVM 19.3 support in our next release (and hopefully GraalVM JDK 11 support too). The concurrency issue is already fixed in GraalVM master, that lets us with the low-level issues. Our goal is to help the GraalVM team understand and fix these issues and get all of this backported to GraalVM 19.3.1.

But more fundamentally, we do not want that to happen again: discovering these late in the game is not fun. To be able to catch these issues earlier, we are setting up a set of CI jobs that will check that the whole Quarkus ecosystem (core extensions + quickstarts + Camel extensions + other external extensions) plays well with GraalVM master. This is a bit challenging as it’s (GraalVM) master on (Quarkus) master on (Apache Camel Quarkus) master, but that’s the only way forward. We have the CI job testing our QuickStart suite with Quarkus master and GraalVM master already.

We also plan to add some RSS usage checks to this CI pipeline. Funny story, we had a different CI job that was testing RSS but its report failed with a NPE. 🤦. Murphy when you hit us.

We hope you understand our cautious stance and the planned delay by a month or so.