In our previous article on the upcoming release of WildFly 11 link - that’s right, at time of writing, it has still not been officially released, just controlled released - we went over a few of the major improvements that have been made to the system.
Improvements we discussed:
- New Security Infrastructure: Elytron
- Request Oriented EJB/JNDI Over HTTP
- Improved EJB / Naming Proxies
In this article we’re going to take a closer look at some of the other improvements on offer.
Improvements to Management and Configuration
Lots to talk about here so let us break it down for you:
Remote managed exploded deployments are new in WildFly 11. This gives remote management clients the ability to update content without a full redeployment. Meanwhile there is also a new management operation to allow reading of individual files within any deployment.
Elsewhere difficult-to-read XML error messages have been banished. No, that doesn’t mean that errors are no longer possible but it does mean that, when they come up, they’ll be easier to read and understand.
Meanwhile CLI tab completion has had an update and can now tab complete attribute reference values that include a range of capabilities.
There is also a new SPI for server extensions. This can be used to register a process state listener and react to server life-cycle changes - super-handy for all kinds of users.
OpenSSL & HTTP/2
New in WildFly 11 is a JSSE provider. This can redistribute TLS handling and remove it from JVM’s internal implementation to one of your system’s OpenSSL libraries. In most cases this should result in a significant improvement on general TLS performance.
Improved Graceful Shutdown/Startup
When it comes to graceful the distributed transactions will be overseen by the graceful shutdown mechanism. Local operations will continue through existing transactions, however, new transactions will be denied.
Meanwhile a new EJB parameter will allow additional remote calls against established or active remote transactions.
As for start-up, the server now does that by entering suspend in the first instance by default. This means you can now use suspended mode to effect any necessary changes. After all services have been launched the server continues the start-up process. Due to this change new requests will not be accepted while the server is starting up.
New Load-Balancer Configs
An additional standalone-load-balancer.xml configuration has been introduced to simply EAP setup as a HTTP load-balancer. The new configuration is dedicated to running just the load balancing services.
Improvements to the Web Console
The Web Console has undergone an overhaul with many helpful improvements. Amongst them are:
- Ability to test data-sources during creation
- Access to recent configuration changes
- Management of Undertow filters
- Active management of JMS transactions
- Management of batch jobs
We’re sure that you, like our instructors, are looking forward to playing with WildFly 11 upon its full release.
Don’t forget that we offer a JBoss EAP 7 (WildFly 10) course that can be tailored to cover topics of your choosing. Get in touch to let us know your needs and we will be happy to discuss the WildFly topics that are most important to you.