WildFly Project News
In this brief demonstration, we’ll set up and run three instances of WildFly on the same machine (localhost). Together they will form a cluster. It’s a rather classic setup, where the appservers needs to synchronize the content of their application’s session to ensure fail over if one of the instances fails. This configuration guarantees that, if one instance fails while processing a request, another one can pick up the work without any data loss. Note...
A recap of the Ask Me Anything session with the WildFly Elytron team that took place this week.
WildFly 27.0.1.Final is now available for download. It’s been about five weeks since the WildFly 27 release, so we’ve done a small bug fix update, WildFly 27.0.1. This includes an update to WildFly Preview. The following issues were resolved in 27.0.1: Bugs [WFLY-17186] - Wrong exception handling by ManagedScheduledExecutorService.schedule(…) [WFLY-17287] - Cannot persist ejb timers into database [WFLY-17313] - Distributed TimerService fails when cache is configured with jdbc-store [WFLY-17350] - Custom mail providers are not...
The WildFly Elytron team will be having an Ask Me Anything session on Monday Dec. 19th on chat.
This article provides details on the new S2I and runtime multi-arch images. New WildFly S2I and Runtime Multi-arch Images These new multi-arch images (linux/arm64 in addition to linux/amd64) have a different naming scheme than the current WildFly images to better handle multiple JDK versions and align with the tag scheme used for the WildFly centos7 docker images (as explained in Updates on WildFly Docker Images blog post). Note The previous WildFly images are now deprecated...
This video provides an introduction to using integrity verification in filesystem realms, a new feature added in WildFly 27.
An overview of the Java Batch Processing API and JBeret implementation.
This video explains how to add upstream repositories, rebase onto upstream branches, and resolve merge conflicts in Git.
Reasons to get involved with the Jakarta EE Specification teams You are a developer that uses the WildFly (Jakarta EE) application server to create/update applications that meet your users needs. Reason #1 is to participate in developing future Jakarta EE releases. From adding a new feature to a specification, to implementing that new feature. You can also help by adding TCK tests for new features as well. Whether you contribute a small or large amount...
