Java News Roundup: GraalVM, Jakarta Data, JNoSQL, Azul Payara

What happened

The week of August 24th, 2026 brought a concentrated wave of Java ecosystem releases, touching runtime infrastructure, cloud runtimes, data access layers, and containerized server distributions. Atmosphere 4.0 reached general availability, GraalVM, Azul Payara, and Quarkus each shipped point releases, WildFly 41 received a maintenance update, Jakarta Data and Eclipse JNoSQL advanced through milestone releases, Open Liberty posted a beta for its September 2026 edition, and Docker images for GlassFish landed publicly.

This article walks through each of those releases — what was delivered, how it affects Java developers and architects building on these runtimes, and what to monitor heading into September. It is aimed at backend engineers maintaining JVM-based services, platform teams evaluating runtime upgrades, and developers who track the Jakarta EE and MicroProfile specification pipelines.

How it works

Atmosphere 4.0 crossed the GA line, making it the first major version increment for the asynchronous web framework in several years. Alongside that headliner, GraalVM, Azul Payara, and Quarkus each published point releases — incremental updates that carry bug fixes, performance tuning, or targeted feature additions without breaking APIs. WildFly 41 issued a maintenance release, indicating ongoing stabilization work on that application server branch. Jakarta Data and Eclipse JNoSQL both advanced to milestone builds, placing them earlier in the release qualification cycle rather than general availability. Open Liberty entered beta for its September 2026 edition, giving adopters a preview window before that month's stable drop. Docker images for GlassFish became available, extending that runtime's distribution footprint into container-native environments.

Why it matters

Atmosphere 4.0 as a GA release signals that its asynchronous and WebSocket programming model is now considered stable for production adoption under that version line, so teams deferring on Atmosphere upgrades have a clear landing point. The GraalVM point release is relevant to anyone using native image compilation or the polyglot runtime, since point releases frequently address correctness issues in ahead-of-time compilation paths that can affect startup behavior or reflection configuration. Azul Payara's point release matters to teams running Payara Server or Payara Micro in commercial environments where Azul's support contract applies. Quarkus point releases typically include dependency updates and extension fixes, so extension authors and application teams should review the changelog for anything touching the extensions they use. The WildFly 41 maintenance release carries significance for organizations still running Jakarta EE workloads on WildFly before migrating to later branches.

Atmosphere 4.0 can be pulled via Maven Central by updating the Atmosphere dependency coordinates in a project's build file to the 4.0 release. GraalVM's point release is available through the GraalVM GitHub releases page and through package managers that track GraalVM distributions. Azul Payara updates flow through Azul's customer portal for licensed subscribers or through standard Payara distribution channels for the open-source tier. Quarkus point releases are available on Maven Central, and projects using the Quarkus BOM need only update the BOM version to pull the aligned set of extension updates. WildFly 41's maintenance release can be downloaded from the WildFly project site. The Open Liberty September 2026 beta is available through the Open Liberty site's beta download section. GlassFish Docker images can be pulled from the image registry referenced in the Eclipse GlassFish project channels.

Who is affected

Jakarta Data is at a milestone build rather than a release candidate or final specification, which means its APIs remain subject to change before the specification concludes. Any production code written against Jakarta Data milestone artifacts carries a migration risk if method signatures or annotation semantics shift in later milestones or the final release. Eclipse JNoSQL is in the same position — milestone status indicates active specification work, and teams evaluating JNoSQL for new data access layers should treat current APIs as provisional. Atmosphere 4.0 being a major version increment means developers upgrading from Atmosphere 3.x should review any breaking changes documented in the migration guide before deploying. GraalVM native image users should run their full test suite after the point release because native compilation is sensitive to runtime changes in reflection and serialization metadata. Open Liberty beta builds are not intended for production use and should only be deployed in evaluation or staging environments.

What to watch next

The Open Liberty September 2026 beta is the most immediate release to track, because its beta window closes when the stable September edition ships, and any feedback on specification behavior or configuration changes needs to land before that cutoff. Jakarta Data and Eclipse JNoSQL milestone progress should be monitored by teams building data access layers, since each subsequent milestone narrows the API surface toward a final specification and gives implementors a clearer integration target. The Quarkus project maintains a release cadence that puts another point release or minor release within weeks, so extension authors should watch the Quarkus GitHub milestones for upcoming changes. GlassFish Docker image adoption will likely drive feedback on container startup configuration and Jakarta EE compatibility in OCI environments, which could surface in bug reports or pull requests over the coming weeks.