
The Payara Monthly Catch -September 2025
Welcome aboard the September issue of The Monthly Catch! With summer holidays wrapping up, the Java world is back […]
Great news for everyone! Today we released a new version of the Payara Platform (5.194) with many exciting new features including production-ready JDK 11 support, Monitoring Console and MicroProfile 3.2 support. This release introduces 50 bug fixes, 13 new features, 20 improvements and 4 component upgrades.
{{cta(‘b2e4c2b6-f33a-4ae4-9290-f1cf476f445a’)}}
Payara Platform 5.194 now supports both JDK 8 and JDK 11 without any changes required on the user side. Keep your eyes out for a dedicated blog post about JDK 11 support coming in the next few days!
Yes, the Monitoring Console is a brand new feature in this release of the Payara Server, as we promised in the Coming Soon article recently! This feature can help you to control the performance of instances managed by the domain. By default it is preconfigured but disabled. You can enable it using this command:
asadmin set-monitoring-console-configuration --enabled true
We implemented support for autoscaling Docker instances, so now you can not only create Docker instances from the DAS but also using plain Docker commands. Name of the instance can be generated automatically.
The start-deployment-group
command received the instanceTimeout
parameter and also the management API now supports deployment groups.
We improved data grid port configuration, so now it respects domain port base and can be also configured individually.
Payara Platform 5.194 now supports MicroProfile 3.2. We implemented changes in Metrics, Config, OpenTracing (find out more here), Rest Client and HealthCheck modules. Find out more about MicroProfile 3.2 support in this blog post.
If you use client certificates for user authentication and authorization, now you can also use the role mapping based on parts of certificate’s distinguished name.
We enhanced the ejb-invoker security configuration, so now you can simply use asadmin commands to configure it.
Now any timeouting transaction will be logged as warning immediately after it timed out and also when the transaction rollbacks, Payara Platform will log also the cause of the rollback.
Some dependencies were updated to newer versions. Especially one update is important – we replaced all Java EE dependencies with their Jakarta EE replacements.
In version 5.194, we changed a lot of Maven group identifiers, most of them have “internal” part now. This means that these identifiers should not be used as dependencies, because they may change in future versions and their API may be very unstable.
We also created the Payara BOM containing all external dependencies of the Payara Server implementation.
Special thanks to svendiedrichsen for following our footsteps and fixing our mistakes so fast! We also owe our thanks to all community members who regularly review our changes or report well reproducible bugs – we wouldn’t be able to make it without you!
For more detailed release notes you can visit this link. Don’t forget to update your Payara Platform to the new version!
{{cta(‘b2e4c2b6-f33a-4ae4-9290-f1cf476f445a’)}}
Share:
Welcome aboard the September issue of The Monthly Catch! With summer holidays wrapping up, the Java world is back […]
We’re excited to announce that Payara Platform Community 7 Beta application server is now fully certified as Jakarta EE 11 […]
The September 2025 release marks a significant milestone with Payara 7.2025.1.Beta1 advancing Jakarta EE 11 readiness, alongside focused improvements […]
What about Open Auth 2 bug fixes. There were lot of issues as unsatisfied dependencies on openauthauthenticationdefinition
Great ! Do you plan to add JDK 11 based Docker images too ? Currently they are Azul JDK 8 only. Thanks
This was going to be my question too. This would be really great.
Thak you, this is great news !!
I mostly use payara through the docker image, do you know if there will be an official jdk11 payara image ?
Hi, great news.
Is this release compatible with OpenJ9?
Greetings
Hi Aleks, I believe it is! Enjoy.
Good news you are creating a BOM. We have been maintaining our own payara-bom up to this point.
In 1.194, regarding Hibernate, there is one issue in JDBCException, that in 1.193 were working fine. When you have one ConstraintViolationException, now it not wrapped correctly, and is wrapped as a NullpointerException.
Hi, could you please create an issue on GitHub with more info and some reproducer? Thank you!