\= Release notes - Payara Platform Enterprise 5.88.0
Behaviour Changes
The default (undefined) value of the fish.payara.ready-after-applications system property will change from false to true starting from 6.42.0, aligning Payara 6 with Community and Payara 7.
The server will mark itself as ready after post-boot configuration is applied and previously deployed applications are loaded, rather than after the server_startup event.
This may change the timing of post-boot scripts and transaction recovery. Ahead of 5.91.0, fish.payara.ready-after-applications can be left unset to adopt the new default, set to true to test the new behaviour early, or set to false to keep the current behaviour.
Bug Fixes
-
[FISH-10485] Fix Payara Micro Boot Properties Not Applied With the Right Timing
-
[FISH-11896] Fix Quoted-Argument Parsing in
prebootCommandFile(asadmin) andPREBOOT_COMMANDS(Docker) -
[FISH-12270] Fix Misleading Log Entries Generated While Configuring Additional Properties for Virtual Servers
-
[FISH-13091] Assorted Deployment Group Fixes
-
[FISH-13137] Fix Prometheus Metrics to Report Histogram Times in Seconds
-
[FISH-13138] Fix Payara Micro’s
--outputlauncherto Respectpayara-boot.properties -
[FISH-13447] Fix Micro
NullPointerExceptionwithlog-to-consoleAccess Log Option