Payara Server 4.1.2.183 Release Notes

This version is distributed only to Payara Enterprise customers

Supported APIs and Applications

  • Java EE 7 Applications

  • MicroProfile 1.4

New Features

Improvements

  • PAYARA-2666 - Show DeploymentException which is hidden behind InvocationException

  • PAYARA-2722 - Notifiers can be made less noisy

  • PAYARA-2733 - Add reasonable default timeouts for Jersey client

  • PAYARA-2744 - Add to the Monitoring REST API Bulk Reading

  • PAYARA-2828 - Add rotation on file size options on Access logging

  • PAYARA-2843 - Add Logging format options to Payara Notification Logger

  • PAYARA-2871 - Improve listing batch jobs memory usage in admin console

  • PAYARA-2889 - Defer Open API scanning to when the /openapi endpoint is first accessed

  • PAYARA-2904 - Remove invalid files from bin directory

  • PAYARA-2961 - Configurations tree view doesn’t list in alphabetically order

  • PAYARA-2966 - Filter healthcheck-list-services and notifier-list-services in default Asadmin recorder config

Bug Fixes

  • PAYARA-2931 - Memory Leak caused by PersistentManager component when enabling file-type session persistence

  • PAYARA-1987 - When using the Admin Console, create-password-alias fails on remote instances

  • PAYARA-2592 - Wrong charset encoding when handling HTTP requests in JAX-RS components through Moxy serialization

  • PAYARA-2635 - HTTP 500 error is thrown when trying to sort instances using node.

  • PAYARA-2724 - Wrong error message when injecting a custom JNDI resource with no defined value

  • PAYARA-2732 - JDBC Connection Pool Flush fails on clustered environment

  • PAYARA-2775 - MP Metrics support for @Stateless JAX-RS resource

  • PAYARA-2784 - Session passivation not working for session file persistence type

  • PAYARA-2788 - Changing port for an non-admin http listener doesn’t work for set-network-listener command

  • PAYARA-2821 - HealthCheck checks send multiple notifications when a new notifier is added

  • PAYARA-2822 - Access logs are not being purged

  • PAYARA-2824 - CDI event bus notifier doesn’t deliver events

  • PAYARA-2825 - Unrecognised element in Payara Micro JDK7

  • PAYARA-2827 - Postboot Command File Parsing Error

  • PAYARA-2830 - StackOverflow error in OpenAPI module

  • PAYARA-2831 - Grizzly Doesn’t Recover From High CPU Load

  • PAYARA-2835 - Client cannot find a secured EJB when running on the same host as the backend

  • PAYARA-2846 - StackOverflowException in OpenAPI

  • PAYARA-2848 - Concurrent Modification Exception in parseBeansXML

  • PAYARA-2849 - PrometheusExporter for MP metrics conversion error

  • [PAYARA-2855 - Spurious SEVERE error messages at deployment

  • PAYARA-2862 - Wildcard in metrics name but not in mbean leads to null pointer and server shutdown

  • PAYARA-2863 - Metrics endpoint displays internal error in case an invalid metric is defined

  • PAYARA-2868 - Duplicate metrics validation

  • PAYARA-2869 - StackTrace Split into Multiple Log Records

  • PAYARA-2870 - Log Formatter Isn’t Used for ConsoleHandler

  • PAYARA-2874 - Enabling Security Manager Causes Log Errors

  • PAYARA-2878 - Applications aren’t Deployed to an Instance with Autobinding Enabled

  • PAYARA-2894 - OpenAPI picks up internal applications when you restart the server.

  • PAYARA-2911 - Can’t set description for JMX Monitoring attributes

  • PAYARA-2920 - OpenAPI has Hardcoded 8080 Port

  • PAYARA-2921 - OpenTracing Swallows StackTraces

  • PAYARA-2923 - IllegalStateException when Running Jax-Rs applications with Request Tracing Enabled

  • PAYARA-2926 - Cookie session persistence type does not throw exception after maxSessions reached

  • PAYARA-2929 - Batch Runtime Configuration has wrong target

  • PAYARA-2931 - Memory Leak caused by PersistentManager component when enabling file-type session persistence

  • PAYARA-2960 - Wrong TLS Protocol Settings for IIOP Listeners

  • PAYARA-2962 - Missing String ConfigProperty should cause DeploymentException

  • PAYARA-3027 - When creating a new standalone instance the HTTP ports are displayed incorrectly

  • PAYARA-3029 - Can not create a new ssh node which is not on the default SSH port

Component Upgrades

results matching ""

    No results matching ""