Release Notes

Payara Platform 5.201

 Payara Server  DownloadDownload Payara Micro

Release Highlights

The release notes of previous releases can be found in the Payara Server Documentation.

Payara Platform 5.201 is the first release of 2020, and it is the release where the Stability and Community streams become synced. (The Community stream are our quarterly public releases and the Stability stream is the monthly bug fix-only releases for those with the supported version of Payara Platform Enterprise). The Stability stream release will form the basis of Payara Platform Enterprise for the coming year.

If you have been using the Derby Database implementation in production, it’s important to note that Derby Database has been removed from the Payara Platform in this release – keep this in mind when upgrading from a previous version.

Included in this release is a tech-preview of Data Grid Encryption, allowing end-to-end encryption of data in Payara’s cluster store. Our blog post Data Grid Encryption Tech Preview in Payara Server 5.201 has all the details.

The Payara Monitoring Console was updated further with more live data on health checks, threads and slow SQL. A new alerts and annotations system and colour themes and settings were added. More details on these new features are found in our post Payara Platform 201 Release – More Updates to Monitoring Console. Furthermore the core of the console was extracted as an independent library and moved to its own top level repository at payara/monitoring-console.

See below for a list of all new features and bug fixes provided in this release including:

 Payara Server  DownloadDownload Payara Micro

New Features

  • [APPSERV-11] – Add Monitoring Console support for reporting healthchecks values
  • [APPSERV-14] – Add Monitoring Console support for identifying slow SQL queries
  • [APPSERV-16] – Add support for encrypting data inside the domain data grid.
  • [APPSERV-19] – Add Monitoring Console Support for Hogging and Stuck Thread Health Checks
  • [APPSERV-47] – Add user defined watches to monitoring console

 Payara Server  DownloadDownload Payara Micro


  • [APPSERV-12] – Change Request Tracing Store Configuration from per Instance to per Cluster
  • [APPSERV-15] – Simplify JMX monitoring and Jolokia configuration
  • [APPSERV-18] – forceName needed for redeployment when deployment descriptor does
  • not specify name
  • [APPSERV-22] – Remove Derby from Payara 5
  • [APPSERV-27] – Allow Temp Docker Nodes to Join a Deployment Group on Creation
  • [CUSTCOM-81] – [Community] GitHub #4386 Debug port is not printed
  • [CUSTCOM-88] – Minor Improvement to DynamicInterceptor Monitoring class
  • [CUSTCOM-145] – Assign meaningful thread names
  • [CUSTCOM-146] – Parameterise CacheMap
  • [CUSTCOM-147] – GH #4418 Improve dependency management of mockito
  • –[CUSTCOM-152] – GitHub #4388 Remove unused field debug from StartServerHelper
  • [CUSTCOM-187] – [Community] Display JVM Uptime in a friendlier format in the Admin Console

 Payara Server  DownloadDownload Payara Micro

Component Upgrades

 Payara Server  DownloadDownload Payara Micro

Bug Fixes

  • [APPSERV-30] – Exception when Adding an Instance to a Deployment Group with an Application Deployed
  • [APPSERV-40] – NPE on starting Payara Micro in JobCleanUpService
  • [APPSERV-87] – Auto-generated name contains a Space
  • [CUSTCOM-13] – A REST management DELETE command returns 415 code instead of 404
  • [CUSTCOM-24] – Persistent EJB Timers are not restored on restart of a Payara Micro instance
  • [CUSTCOM-27] – [Community: sergitrujillo] Steady pool size should allow zero
  • [CUSTCOM-53] – Wrong error message when a JDBC pool with size 0 is created.
  • [CUSTCOM-54] – NullPointerException when JMX attribute is null within the rest-monitoring endpoint
  • [CUSTCOM-56] – [Community: pzygielo] Production domain.xml in Payara Web Profile is unparseable
  • [CUSTCOM-70] – JAX-RS client request with payara-embedded raises IllegalStateException for
  • RequestTracingService run level
  • [CUSTCOM-71] – Multiple realm identity store annotations are ignored
  • [CUSTCOM-75] – Problem in Payara 5.194 setting port overrides via configuration > system properties resets other overrides
  • [CUSTCOM-76] – Incorrect thread synchronization in WebappClassLoader
  • [CUSTCOM-78] – Redeployment on deployment groups is broken
  • [CUSTCOM-83] – Grizzly Infinite Loop Causing CPU Hogging
  • [CUSTCOM-109] – SendAsadminCommand throws NPE if there are no explicit targets
  • [CUSTCOM-135] – Domain Startup Failure on slow or busy environments
  • [CUSTCOM-142] – Unable to use delete-jvm-options on option with min/max version defined.
  • [CUSTCOM-144] – [Community: pzygielo] NPE in FilterDefDecorator
  • [CUSTCOM-165] – JDK11 prints warning about illegal access to private field props of the LogManager
  • [CUSTCOM-167] – [Community: pzygielo]  Code cleanup – removed unused cycles
  • [CUSTCOM-168] – [Community: parysto] OpenID Connect: Fixed simultaneous redirects and invalidation of session
  • [CUSTCOM-171] – [Community: pzygielo] BlockingQueueHandler throws ClassCastException
  • [CUSTCOM-174] – NPE on EJBException.addSuppressed() within EJBContainerTransactionManager
  • [CUSTCOM-181] – [Community] GH #4444 PR – Remove unused method with potential ClassCastException
  • [CUSTCOM-195] – Building of domain module fail when port 7676 is in use
  • [CUSTCOM-198] – [Community] OpenAPI document generation ignores @Schema(ref) value
  • [CUSTCOM-199] – REST Management Interface Can’t Be Invoked With JSON Request
  • [CUSTCOM-200] – [Community] Unused timer var in HazelcastTimerStore.cancelTimersByKey
  • [CUSTCOM-203] – [Community] OpenAPI Incorrect $ref Field with Custom Schema Name
  • [CUSTCOM-204] – [Community] Incorrect TreeSet Comparator Implementation

 Payara Server  DownloadDownload Payara Micro

Supported APIs and Applications

  • Java EE 8 Applications
  • Jakarta EE 8 Applications
  • MicroProfile 3.2

Community Contributions

Community icon

The Payara Platform is open source and includes improvements and fixes provided by community contributions along with those created by our engineering team.

Thank you to GitHub users for your contributions to this release:

Learn How to Get Involved

Back to top