Hello Wildfly devs,
At my job we want to move to Linux ARM64 machines for our deployments.
The issue we see is that the current (22.0.1) distribution does not include
native binaries for linux-aarch64 architecture :-/
$ find ./ -name "*.so"
I've found https://issues.redhat.com/browse/WFLY-13302 (and
https://issues.apache.org/jira/browse/ARTEMIS-2705) but those are opened
almost an year ago and it is not clear whether they will be resolved any
As far as I understand your recommendation is to build the binaries
locally. This is OK but it adds some extra complexity to the deployment and
Since ARM64 becomes more and more popular for server side deployments I
would like to ask you whether those tickets could be resolved in near
There are a lot of changes coming in WildFly as we move on from legacy
security, pivot toward Jakarta EE 10 and the jakarta.* package namespace,
and keep up with progress in Java SE. I've blogged about how I see things
changing in WildFly over the next few releases. See
I'd love to hear your thoughts and questions about all of this!
Project lead -- WildFly
I am pleased to announce that the WildFly 25.0.0.Beta1 release is now
available at https://wildfly.org/downloads/
This has been a busy release so there is plenty of information available at
some highlights are:
- A new subsystem providing support for OpenTelemetry Tracing
- A new subsystem that provides native support for OpenID Connect
- An update of the MicroProfile Reactive Messaging subsystem to version
2.0 of the specification.
- Updates to allow the same expression to be resolved either as a system
property or environment variable.
- Removal of legacy security integration.
- Progress towards Java SE 17 support.
- And plenty more.
Please try out the release and give us your feedback. In the meantime we
are working towards the Final release of WildFly which we anticipate to be
around the 30th September.
Red Hat <https://www.redhat.com/>