The November 2025 release brings significant milestones across the Payara Platform family. This month includes Payara Platform Community 6.2025.11, Enterprise 6.32.0, Enterprise 5.81.0, and the highly anticipated Payara Platform Community 7.2025.1, our first official Jakarta EE 11 certified release. Download Payara Platform here.
The headline achievement this month is Payara Platform Community 7.2025.1 (download here) achieving official Jakarta EE 11 certification. This release represents a major milestone in enterprise Java, bringing support for Jakarta EE 11 and MicroProfile 6.1 to production-ready status.
This release also completes the removal of the legacy Monitoring Console, streamlining the platform for modern observability implementations. Teams can now start developing Jakarta EE applications on the Payara Platform.
Key Bug Fixes
Virtual server configurations now remain stable when redeploying applications to deployment groups used as Default Modules. Previously, such redeployments could break virtual server settings, causing routing issues in multi-tenant environments.
Virtual Threads configuration changes now properly indicate when server restarts are required. This fix prevents confusion around when Virtual Threads settings actually take effect, ensuring predictable threading behavior.
An unexpected BASIC authentication prompt appearing with HTTPS connections during domain initialization has been resolved. This fix eliminates authentication challenges that occurred during server startup in secure environments.
Component Upgrades
Payara 7.2025.1 received comprehensive component updates reflecting Jakarta EE 11 requirements. Notable upgrades include:
Core Jakarta EE 11 Components:
- Mojarra to 4.1.4 with reapplied patches
- EclipseLink patches reapplied for Jakarta EE 11 compatibility
- OpenMQ to 6.7.0 with patches
- Grizzly version corrections with patches
- Hibernate Validator to 9.0.1
Infrastructure Components:
- Jersey 4.0.0-M2.payara-p1
- HK2 4.0.0-M3.payara-p1
- Expressly 6.0.0-M2
- Concurro 3.1.0 Final
- Jakarta Faces 4.1.2
Supporting Libraries:
- osgi-resource-locator to 3.0.0
- woodstox-jsf to 6.0.1
- Jakarta Validation to 3.1.1
- Jakarta Authorization to 3.0.0
- JakartaEE API to 11.0.0.RC1
- wasp 4.0.0
- glassfish-management 3.3.0.payara-p1
- logging-annotation-processor 1.10
- jsftemplating 4.1.0-M1
- hk2-core 2.4.0-b14
Docker images feature JDK 21.0.9, reflecting the latest Java security patches and performance improvements.
Community 6.2025.11 introduces a –no-validation flag for JDBC connection setup, allowing faster configuration when connection parameters are already validated. This addition speeds up automated deployment scripts and infrastructure-as-code workflows.
Critical Bug Fixes
PrimeFaces Autocomplete Fix: PrimeFaces Autocomplete components in composite components now function correctly when upgrading from Payara 4.x to Payara 6. This fix resolves select event handling that broke during major version upgrades.
Versioned Deployment Routing: Versioned deployments now route correctly after undeploying older versions. Previously, undeploying outdated application versions could break routing to active versions, causing HTTP 503 errors.
High-Load Stability: High-load scenarios no longer trigger “Could not find an implementation of ClassAnalyzer with name CdiInjecteeSkippingClassAnalyzer” errors. This fix improves stability in production environments experiencing traffic spikes.
OpenAPI Generation: OpenAPI generation now works correctly when bean validation is used without PathParam annotations, ensuring proper API documentation for all endpoint types.
Component Upgrades
Core libraries received targeted updates:
- ASM from 9.8 to 9.9
- Eclipse Persistence ASM from 9.8.0 to 9.9.0
- Apache BCEL from 6.10.0 to 6.11.0
- Reactor Core from 3.7.11 to 3.7.12
- HK2 to 3.1.1
Docker images include JDK 21.0.9, JDK 17.0.17, and JDK 11.0.29, ensuring containerized applications benefit from the latest Java security patches.
Enterprise 6.32.0 mirrors Community 6.2025.11’s –no-validation flag for JDBC connections while adding an exclusive fix for Payara Micro custom error page configurations.
This edition resolves all the same critical bugs as Community 6.2025.11:
- PrimeFaces Autocomplete issues
- Virtual server deployment problems
- Versioned deployment routing failures
- High-load ClassAnalyzer errors
- OpenAPI generation with bean validation
Component upgrades match Community 6.2025.11, including ASM 9.9, Eclipse Persistence ASM 9.9.0, Apache BCEL 6.11.0, Reactor Core 3.7.12, and HK2 3.1.1. Docker images feature JDK 21.0.9, JDK 17.0.17, and JDK 11.0.29.
Enterprise 5.81.0 (get free trial here) maintains Jakarta EE 8 compatibility while providing the same –no-validation flag for JDBC connections introduced in other editions. This release addresses virtual server deployment group issues and versioned deployment routing failures that affect Jakarta EE 8 environments.
Component Upgrades
Component upgrades focus on stability:
- ASM 9.9
- Eclipse Persistence ASM 9.9.0
- Apache BCEL 6.11.0
- Reactor Core 3.7.12
Docker images include JDK 21.0.9, JDK 17.0.17, JDK 11.0.29, and JDK 8u472 for organizations maintaining Java 8 applications.
Release Notes
Get Started Today
Start Exploring Jakarta EE 11: Payara Platform Community 7.2025.1 enables development teams to begin building and testing Jakarta EE 11 applications in development environments. Explore the latest enterprise Java specifications while your production workloads continue running on proven platforms. Find out more about Jakarta EE.
Production Environments: Payara Platform Enterprise 6.32.0 and 5.81.0 provide comprehensive support, guaranteed stability, and 24/7 assistance for mission-critical applications. Keep your production systems running on Jakarta EE 10 or Jakarta EE 8 while your teams gain experience with Jakarta EE 11 in parallel development environments. Get your free trial here.
Flexible Modernization Path: Organizations can now maintain their existing production workloads on Enterprise editions while development teams experiment with Jakarta EE 11 features using Community 7.2025.1. This approach allows gradual adoption of new specifications without disrupting business operations.
Upgrading
We recommend upgrading production environments to Enterprise 6.32.0 or 5.81.0 to benefit from JDBC configuration improvements, deployment stability fixes, and component updates. The virtual server and versioned deployment fixes make this upgrade particularly valuable for multi-tenant and blue-green deployment scenarios.
Development teams should download Community 7.2025.1 to start exploring Jakarta EE 11 capabilities and planning future migration strategies.
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.
Happy deploying!
5 minutes
