
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 […]
The October 2025 release brings focused improvements across Payara Platform Community 6.2025.10 (download here), Payara Platform Enterprise 6.31.0 (download trial here), and Enterprise 5.80.0. This month’s updates center on deployment flexibility, admin interface performance, and stability fixes that address several long-standing issues.
Community Edition 6.2025.10 extends the warlibs functionality to the deploy-remote-archive command. This improvement allows applications deployed from remote locations to take advantage of shared library directories, reducing deployment package sizes and improving deployment speed across distributed environments.
All editions now support configurable cache time-to-live settings for application deployments, thanks to community contributor Lenny Primak. This addition provides fine-grained control over how long deployment artifacts remain cached, allowing teams to optimize memory usage and deployment behavior for their specific requirements.
A significant issue where saving batch settings for Payara Server instances created duplicate domain.xml entries has been resolved. These duplicates prevented server startup, causing disruption in environments where batch job settings were modified. This fix ensures clean configuration updates across all server management operations.
The admin interface now responds normally when managing degraded server instances. Previously, administrators experienced slow response times when interacting with instances in degraded states, hampering troubleshooting efforts during critical situations. This improvement restores efficient management capabilities regardless of instance health.
Payara 5.69+ experienced breaking changes when applications enabled Jackson’s FAIL_ON_TRAILING_TOKENS feature. This release restores proper deserialization behavior, ensuring applications can enforce strict JSON parsing without encountering unexpected failures.
JNDI lookups for local JavaMail sessions now work correctly. This fix resolves authentication and connection issues for applications relying on locally configured email sessions, particularly important for notification systems and automated reporting functions.
The Phone Home feature no longer generates duplicate installation identifiers. This correction ensures accurate telemetry data and prevents confusion when tracking Payara Platform deployments across your infrastructure.
All editions received comprehensive component updates to maintain security and compatibility. Notable upgrades include
For complete details on all component upgrades, refer to the Release Notes – Enterprise & Community.
Special thanks to Lenny Primak for implementing the cache time-to-live configuration feature. Community contributions continue driving Payara Platform forward with practical enhancements that benefit production deployments.
We recommend upgrading to these latest releases to benefit from the domain configuration stability fixes, admin interface performance improvements, and component updates. The batch settings fix alone makes this upgrade important for environments using batch job processing.
For detailed upgrade instructions, please visit our official documentation.
Your feedback drives our innovation. Report issues and share experiences on our GitHub repository. Thank you for your continued support of the Payara Platform!
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 […]
Managing Payara Server Just Got Smarter Imagine managing your Jakarta EE applications not just with Maven goals, but by […]