Skip to content

Releases: payara/Payara

Payara Server Community Edition 5.2020.6

11 Nov 11:00
b362f64
Compare
Choose a tag to compare

Payara Server Community Edition 5.2020.5

12 Oct 09:08
07f5cf1
Compare
Choose a tag to compare

Release Notes

Notes

Tech Preview: Run Jakarta EE 9 Applications

This release includes tech preview functionality to run Jakarta EE 9 applications on Payara Server and Payara Micro. This does not, however, make this edition of Payara Platform Community Jakarta EE 9 compatible, and we do not recommend using this functionality in production at this time. This should not affect the ability to run Jakarta EE 8 applications. See ‘FISH-256’ for more details.

New Notifier Extensions

FISH-315 gave the notification service a major overhaul that makes implementing new notifiers in a modular fashion easier. This has facilitated the rewrite of the notifiers as extensions (https://github.com/payara/Notifiers) and the implementation of new Discord (FISH-471) and Microsoft Teams (FISH-370) notifiers. Note that the notifiers that were previously removed from Payara Platform Community Edition (now found at the above link) are still available by default in Payara Enterprise Edition.

New Features

  • [FISH-256] - Identify, Transform, and Run jakarta.* application (Tech Preview Only)

  • [FISH-333] - Add MicroProfile Health Readiness Checks

  • [FISH-370] - Add Microsoft Teams Notification channel

  • [FISH-471] - Add Discord Notification Channel

Improvements

  • [FISH-141] - Support additional fields with LogRecord when using JsonLogFormatter

  • [FISH-154] - Support log-jdbc-calls attribute in xml used by asadmin commands create-jdbc-connection-pool and add-resources (through xml)

  • [FISH-315] - Implement New Public Notifier API

  • [FISH-316] - Upgrade New Relic Notifier to Implement New Notifier API

  • [FISH-317] - Upgrade XMPP Notifier to Implement New Notifier API

  • [FISH-318] - Upgrade SNMP Notifier to Implement New Notifier API

  • [FISH-319] - Upgrade Slack Notifier to Implement New Notifier API

  • [FISH-320] - Remove Hipchat Notifier

  • [FISH-321] - Upgrade Datadog Notifier to Implement New Notifier API

  • [FISH-322] - Upgrade Email Notifier to Implement New Notifier API

  • [FISH-323] - Upgrade JMS Notifier to Implement New Notifier API

  • [FISH-324] - Upgrade Eventbus Notifier to Implement New Notifier API

  • [FISH-325] - Upgrade CDI Eventbus Notifier to Implement New Notifier API

  • [FISH-389] - Add Transaction ID as a Baggage Item to Spans

  • [FISH-426] - Store initial request path when accessing protected resource with OpenIdAuthenticationMechanism

  • [FISH-441] - StatsProviderManagerDelegate should write warning instead of throwing Exception when stats provider info is not found.

  • [FISH-449] - Oracle 19C Not Autodetected by EclipseLink

  • [FISH-459] - Cleanup of sonar warnings in jdbc40 module

Security fixes

  • [FISH-381] - Upgrade Nimbus JOSE+JWT to 8.20

Bug Fixes

  • [FISH-25] - SOAP Web Service Tester not working correctly (JDK 11)

  • [FISH-37] - @DataSourceDefinition passes serverName and url to DataSource in some cases

  • [FISH-48] - OpenAPI document failed to use Generics within @Schema

  • [FISH-55] - Creating Java Mail Session targetted to Deployment Group fails

  • [FISH-59] - Payara Micro --enableRequestTracing argument not accepting values

  • [FISH-66] - Zip file closed on EJB initialization

  • [FISH-82] - Command Line option --warmup results in an Exception when Payara Micro instance stops when Request Tracing is activated

  • [FISH-89] - Possible NPE in request tracing during startup

  • [FISH-90] - wscompile NoClassDefFoundError with jdk 8

  • [FISH-93] - wsgen NoClassDefFoundError with jdk 11

  • [FISH-99] - OpenAPI APIResponse.Content.Schema sometimes shows only partial result

  • [FISH-196] - EJB injection in EJB Stateless based JAX-RS resource doesn't work in EAR.

  • [FISH-198] - IllegalArgumentException on accessing the deploy asadmin REST endpoint with upload flag

  • [FISH-298] - OpenAPI @Schema implementation is ignored

  • [FISH-379] - Admin Console Masthead Looks Different Between Firefox and Chrome

  • [FISH-388] - Fix NPE when printing out Active Span

  • [FISH-391] - OutOfMemoryError exception caused by OpenApi refactor

  • [FISH-392] - Trace gets started even when RequestTracing is disabled.

  • [FISH-393] - asadmin command list-rest-endpoints doesn't list PATCH methods

  • [FISH-396] - When _JAVA_OPTIONS specified, Payara Server incorrectly detects Java version for JVM options

  • [FISH-407] - List of enabled application targets are not always correct

  • [FISH-446] - [Community Contribution: svendiedrichsen] Access to /metrics endpoint may cause ConcurrentModificationException

  • [FISH-447] - TCK Failure Websocket module. Relates to HTTP2

  • [FISH-474] - Admin Console doesn't display JDK distribution specified for a JVM option

  • [FISH-477] - Deployment Group Properties are Ignored

  • [FISH-509] - Deployment failure due to 'The lifecycle method [postConstruct] must not throw a checked exception.'

Component Upgrades

Payara Server Community Edition 5.2020.4

14 Aug 09:13
Compare
Choose a tag to compare

Release Notes

New Features

  • [FISH-8] - Add-Widget-Wizard
  • [FISH-244] - Expand Open Tracing Support across Remote EJB Calls

Improvements

  • [FISH-257] - Domain Status Indicator
  • [FISH-266] - Remove New Relic Notifier
  • [FISH-267] - Remove XMPP Notifier
  • [FISH-268] - Remove SNMP Notifier
  • [FISH-269] - Remove Slack Notifier
  • [FISH-270] - Remove HipChat Notifier
  • [FISH-271] - Remove Email Notifier
  • [FISH-272] - Remove Datadog Notifier
  • [FISH-273] - Remove Yubikey Authentication Mechanism
  • [FISH-314] - Add TLS 1.3 support for OpenJDK 8

Bug Fixes

  • [FISH-35] - Payara Micro system property payaramicro.logPropertiesFile and payaramicro.enableAccessLog do not work
  • [FISH-45] - The Jackson-dataformat-XML OSGi module cannot be resolved in Payara 5
  • [FISH-53] - Using Span.finish() doesn't finish a Propagated Span
  • [FISH-68] - @DatasourceDefinition not picking MicroProfile Configuration properties
  • [FISH-342] - Community Contribution: CopyOnWriteArrayList throws expected exceptions in WebdavServlet

Component Upgrades

  • [FISH-287] - Update Monitoring Console to 1.3

Payara Server Community Edition 5.2020.3

17 Jul 16:58
c9a8ca7
Compare
Choose a tag to compare

Release Notes

Improvements

  • [FISH-6] - Multiple Data Series in a Graph
  • [FISH-31] - HTTP/2 Support for JDK Native ALPN APIs
  • [FISH-128] - OpenAPI does not include APIs from jars within a war (other jars)
  • [FISH-148] - Support multirelease JARs in WARs
  • [FISH-151] - Implement MicroProfile JWT-Auth 1.1.1
  • [FISH-171] - Support for multi HTTPAuthenticationMechanism
  • [FISH-205] - Allow dynamic reconfiguration of log levels for Payara Micro instance
  • [FISH-208] - Improvements in stop-domain process
  • [FISH-219] - Indicate missing default value when using custom template for create-domain

Bug Fixes

  • [FISH-42] - OpenAPI document has duplicate Tag items
  • [FISH-50] - JDK11 illegal reflective access by OpenAPI document generation
  • [FISH-56] - OpenAPI document doesn't use @Schema when class is in jar dependency of the project
  • [FISH-70] - JsonArray as return type breaks the OpenAPI document generation
  • [FISH-92] - OpenAPI document fails for bidirectional references
  • [FISH-197] - JDBCRealm requires the Message Digest field although a default value should be used
  • [FISH-207] - Disabling applications via their deployment group targets not working
  • [FISH-211] - PayaraMicro APIs not initializable when run via RootLauncher
  • [FISH-236] - GitHub #4688 Typo in docker file - removal of /tmp/tmpfile
  • [FISH-260] - Missing invocation on top of invocation stack
  • [FISH-263] - Community Contribution: NPE when enabling versioned application with Microprofile Config

Component Upgrades

  • [FISH-243] - Update Monitoring Console Process to 1.2.1

Payara Server Community Edition 5.2020.2

19 Jun 10:10
170fc8a
Compare
Choose a tag to compare

Release Notes

Notes

CUSTCOM-40 Upgraded Yasson to version 1.0.6, which introduced some breaking changes in Payara 5.2020.2 - take caution when upgrading.

New Features

  • [APPSERV-20] - MicroProfile ConfigSource for Payara Variable Expressions
  • [APPSERV-124] - Monitoring Console: Server Side Configuration and Sharing
  • [APPSERV-149] - Add Command to Generate Self-Signed Certificate

Improvements

  • [APPSERV-54] - Print a Warning if Data Grid Encryption is Enabled without a Key
  • [APPSERV-57] - MicroProfile Fault Tolerance 2.1
  • [APPSERV-58] - MicroProfile Config 1.4
  • [APPSERV-59] - MicroProfile Metrics 2.3
  • [APPSERV-60] - MicroProfile Health 2.2
  • [APPSERV-61] - MicroProfile Rest Client 1.4
  • [APPSERV-141] - Add Caching to MicroProfile Config
  • [APPSERV-143] - Update Enterprise and Community Branding
  • [APPSERV-146] - Monitoring Console: Bookmarkable Page URLs
  • [APPSERV-148] - Monitoring Console: MP Metrics Metadata as MC Annotations
  • [CUSTCOM-166] - CDI deployment failure when to use @RolesPermitted in Faces backing bean
  • [CUSTCOM-235] - Stop Hazelcast being started twice to improve Micro boot times
  • [CUSTCOM-238] - Support JSP on Payara Micro Docker

Bug Fixes

  • [APPSERV-55] - Fix Fault Tolerance Bulkheads Race Conditions
  • [APPSERV-114] - Race condition in InvocationManager
  • [APPSERV-142] - Payara Micro doesn't shutdown when invoked with –warmup
  • [CUSTCOM-12] - Unexpected errors when updating SSH node security properties
  • [CUSTCOM-22] - HTTP/2 Push Can't be Disabled
  • [CUSTCOM-133] - Accessing a URL before any application is deployed disables JASPIC SAM authentication
  • [CUSTCOM-179] - PrimeFaces AutoSelect Event is Null within Custom Component
  • [CUSTCOM-194] - The delete-jvm-options command shouldn't require to specify the Java version prefix
  • [CUSTCOM-205] - On ZuluJDK 8.44, accessing HTTPS gives NoSuchMethodError
  • [CUSTCOM-213] - generate-encryption-key Command Always Creates Key for Default Domain
  • [CUSTCOM-219] - Fix support for set-batch-runtime-configuration --schemaName for MySql and Postgres
  • [CUSTCOM-223] - Datagrid Encryption Enabled Message Printed even if it isn't
  • [CUSTCOM-237] - In Weld, parallel execution mode for async observers doesn't trigger all observers (IllegalStateException: Security context is already associated)
  • [CUSTCOM-247] - Custom realm defined in web.xml isn't used for SOAP services secured using WS security policy
  • [CUSTCOM-253] - Patch ArrayIndexOutOfBoundsException defect in Mojarra
  • [CUSTCOM-254] - NumberFormatException when parsing a HTTP header in metrics
  • [CUSTCOM-260] - {Community - sgflt] - Deadlock in HA session management
  • [CUSTCOM-261] - Remove jakarta.transaction.cdi:jakarta.transaction.cdi-api from Payara BOM as it is wrong
  • [CUSTCOM-262] - HZ_LISTENER_PORT property error when setting system properties via the admin console
  • [CUSTCOM-263] - HTTPS doesn't work on JDK 8u252
  • [CUSTCOM-264] - Client mode debugging (server=no) doesn't work with JDK>=9
  • [CUSTCOM-265] - Starting the domain with JSON Log formatter causes the server log to rotate
  • [CUSTCOM-266] - JSP/JSF startup issues when using Payara Micro RootDir launcher
  • [CUSTCOM-271] - Metric endpoint fails to parse Accept header from Telegraf
  • [CUSTCOM-273] - Support for all AjaxBehaviourEvent classes, extension to CUSTCOM-179
  • [CUSTCOM-284] - Remove Expired Certificates
  • [ECOSYS-157] - OpenID Connect Caller's name and groups are null
  • [ECOSYS-161] - [Community - NikitaZ] OAuth2AccessToken empty instance injected

Component Upgrades

Payara Server 5.201

27 Feb 12:24
Compare
Choose a tag to compare

Release Notes

Supported APIs and Applications

Java EE 8 Applications

MicroProfile 3.2

Jakarta EE 8 Applications

Notes

Derby Database has been removed from the Payara Platform in this release – keep this in mind when upgrading from a previous version in the case that you have been making use of the Derby Database implementation in production previously

New Feature

  • [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

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] 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] 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] NPE in FilterDefDecorator
  • [CUSTCOM-165] - JDK11 prints warning about illegal access to private field props of the LogManager
  • [CUSTCOM-167] - [Community] Code cleanup - removed unused cycles
  • [CUSTCOM-168] - [Community] OpenID Connect: Fixed simultaneous redirects and invalidation of session
  • [CUSTCOM-171] - [Community] 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

Improvements

  • [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

Component Upgrade

Payara Server 5.194

29 Nov 17:19
25b9080
Compare
Choose a tag to compare

Release notes

JDK11

Payara Server on JDK11 will no longer be in technical preview with the 5.194 release! This means you are now able to use Payara in Production on JDK11 confidently.

Note

Metrics includes some breaking changes related to the refactoring of counters (see spec for more details).

New Features

  • [PAYARA-3924] - Publish Payara third-party BOM
  • [PAYARA-2598] - Hook up Soteria Identity Stores to Payara Realms
  • [PAYARA-3263] - Support Certified OpenTracing Tracers in MP OpenTracing
  • [PAYARA-3658] - Add support for easily securing the ejb-invoker endpoint
  • [PAYARA-3793] - Role mapping can be based on partial DN name (Client Certificates)
  • [PAYARA-3828] - REST Client 1.3 support
  • [PAYARA-3829] - Healthcheck 2.1 support
  • [PAYARA-3832] - Add Monitoring Console support for identifying which traces have exceeded thresholds
  • [PAYARA-3994] - HotDeploy support in deploy/redeploy asadmin command
  • [PAYARA-4027] - Add timeout parameter to start-deployment-group command
  • [PAYARA-4037] - Add access log setting options for Payara Micro
  • [PAYARA-4097] - Add Monitoring Console support for launching with a preset of 5 key metrics
  • [PAYARA-4166] - Metrics 2.2 Support

Improvements

  • [PAYARA-3796] - Can't inject a JNDI Integer property as MicroProfile config value
  • [PAYARA-3811] - Improve Application Deployment Performance (Pt2.) on Windows OS
  • [PAYARA-3819] - Remove java.net repositories from pom
  • [PAYARA-3940] - Classloader whitelisting mechanism should isolate resources too
  • [PAYARA-3997] - Add TLS 1.3 support when using Zulu JDK 8
  • [PAYARA-4033] - Remove duplicate classes for remote commands
  • [PAYARA-4096] - Allow Instance Names to be Generated when Creating Instances from the Admin Console
  • [PAYARA-4099] - Add support for autoscaling Docker Nodes
  • [PAYARA-4118] - Graceful shutdown of PayaraExecutorService slows down server shutdown
  • [PAYARA-4143] - Community Contribution: Replace usage of File.deleteOnExit() with manual deletion on exit.
  • [PAYARA-4158] - Domain Data Grid Port Behaviour options for create-domain command
  • [PAYARA-4171] - Monitoring data of an Instance is not visible if it is in a Deployment Group
  • [PAYARA-4192] - Support explicitly setting Data-Grid port in an instance
  • [PAYARA-4193] - Additonal Improvements for Monitoring Console Preset Page
  • [PAYARA-4195] - Cleanup in deployment-client
  • [PAYARA-4197] - Improve logging warnings for container-managed transaction timeouts
  • [PAYARA-4247] - Cleanup of sonar warnings for common/common-util
  • [PAYARA-4248] - Log Expired certificates from cacerts.jks with level warning
  • [PAYARA-4251] - Simplify Woodstock upgrades

Bug Fixes

  • [PAYARA-1285] - Thread Pool monitoring breaks when configuring thread pools
  • [PAYARA-3500] - Admin console shows incorrect virtual servers for MP health and metrics targets
  • [PAYARA-3501] - Configuration changes in MP health and metrics in Admin console don't warn about restart needed
  • [PAYARA-3803] - Illegal Reflective Access by com.sun.enterprise.admin.util.JarFileUtils
  • [PAYARA-4025] - REGRESSION: Setting context root with app.war:context stopped working in Payara Micro 5.192
  • [PAYARA-4048] - ejb32/mdb/modernconnector fails
  • [PAYARA-4055] - Jaxrs client obtained from the request context must be the same instance
  • [PAYARA-4061] - jsp test failures
  • [PAYARA-4077] - CDI test EnterpriseSecurityContextPropagationInAsyncObserverTest fails
  • [PAYARA-4078] - CDI InterceptorEnvironmentJNDISessionBeanTest fails
  • [PAYARA-4083] - Unsatisfied dependencies for type YubicoAPI in CDI TCK
  • [PAYARA-4087] - Allow use of single char operands in payara micro commands
  • [PAYARA-4104] - Disabling Hazelcast for 5.193 Server causes startup failure
  • [PAYARA-4115] - List-Nodes-Docker Command Fails with Invalid Number of Columns
  • [PAYARA-4116] - Server shutdown hangs when startup fails
  • [PAYARA-4120] - Server fails to start when using JDK11
  • [PAYARA-4121] - Monitoring Configuration Level Ignored after Redeploying an Application
  • [PAYARA-4122] - Unable to acquire global lock for resolve payara-micro-service
  • [PAYARA-4123] - Async errors are missing in resumed response
  • [PAYARA-4124] - Application name of deployed ear shows the unique number
  • [PAYARA-4125] - MP HealthCheck NPE from when first saving values in admin console
  • [PAYARA-4129] - Payara-samples were not updated after release of 5.193
  • [PAYARA-4131] - java.lang.ClassNotFoundException: org.glassfish.admin.rest.resources.generatedASM.DomainResource not found by org.glassfish.main.admin.rest-service
  • [PAYARA-4140] - ResourceValidator fails on jms/ee20/cditests/ejbweb
  • [PAYARA-4141] - Use correct constructor of NotAuthorizedException in RolesPermittedInterceptor
  • [PAYARA-4144] - Add support for Deployment Group on Management API
  • [PAYARA-4146] - JavaMail Fails to Load Default Providers
  • [PAYARA-4147] - MicroProfile Metrics API returns no data for vendor:system_cpu_load
  • [PAYARA-4160] - Admin Console List EJB Timers Causes HTTP 500
  • [PAYARA-4164] - OpenTracingApplicationEventListener is not null-safe
  • [PAYARA-4167] - JSON-B Runtime not present on AppClient classpath
  • [PAYARA-4169] - Incorrect server.policy settings
  • [PAYARA-4170] - Deployment-client breaks TCK tests
  • [PAYARA-4172] - Generation of OpenAPI document when using @Schema(implementation) sometimes give wrong result
  • [PAYARA-4174] - CDI injection gives IllegalStateException on MP Metrics bean in Payara Micro
  • [PAYARA-4186] - OpenAPI document generates incorrect schema for Enums
  • [PAYARA-4196] - Monitoring console throws error when dealing metrics that include a space
  • [PAYARA-4202] - Arrays not supported in PayaraConfig.getOptionalValue()
  • [PAYARA-4206] - MP Config does not support char as type of property
  • [PAYARA-4207] - Steady pool size should allow zero
  • [PAYARA-4215] - Database EJB Timer Persistence Service doesn't work on Deployment Group
  • [PAYARA-4218] - JAX-WS Command Error
  • [PAYARA-4219] - Problem when trying to override System Properties of an instance
  • [PAYARA-4238] - Monitoring Console Hardening
  • [PAYARA-4250] - Monitoring Console - Prevent Log Spamming
  • [PAYARA-4253] - Update TCK signature tests for 5.194
  • [PAYARA-4254] - Test failure in ejb32 / modernconnector
  • ...
Read more

Payara Server 5.193

28 Aug 12:05
Compare
Choose a tag to compare

Notes

JDK11

In this release, JDK11 support is still in tech preview. Although it may work without problems in production we cannot guarantee that this will be the case.

Guava Removal

PAYARA-3939 removed Guava from the Payara codebase. This is important when upgrading your domain since previously if application used Guava it may have worked with Guava as only a compile dependency. After upgrading this will not be the case, and you should provide Guava yourself.

Master Password Changes

PAYARA-4031 addressed a problem with changing the master password for nodes. In previous releases, changing the master password for only a domain before attempting to start an instance on another node would render that instance unusable. This fix changed the functionality of running change-master-password against a node. It now will not interact with any keystores, only the saved password file. This makes the master password change work the way we believe was originally intended: you need to run the command against each node after changing the domain master password before starting those instances.

New Features

  • [PAYARA-3573] - Dynamic Instances
  • [PAYARA-3830] - Support Metrics 2.0
  • [PAYARA-3850] - Aggregate data onto Monitoring App
  • [PAYARA-3864] - Support Java Serialization in EJB HTTP Client
  • [PAYARA-3876] - Add profiles for building dev version of Payara with full source embedded
  • [PAYARA-3885] - Implement "Parameterized" dynamically resolved role names for @RolesPermitted annotation

Improvements

  • [PAYARA-3218] - Add Deployment Performance Analyzer
  • [PAYARA-3492] - Upgrade JLine version to v3.x
  • [PAYARA-3691] - Support reading WSDL files from WEB-INF
  • [PAYARA-3792] - asadmin command to return the DN of Client Certificate
  • [PAYARA-3821] - Add asadmin command to reset AMX metrics
  • [PAYARA-3824] - Use KeyID from JWT header to find public key in JSON Web Key Set [Community Contribution: lreimer]
  • [PAYARA-3825] - Validity check and auto-refresh for OpenID connect tokens. [Community Contribution: parysto]
  • [PAYARA-3868] - Repeated NPE printed to console with Payara Micro after sitting idle
  • [PAYARA-3883] - Move the groupsearcherror to a separate logger
  • [PAYARA-3902] - Support protocol V1 for JSON-B serialization
  • [PAYARA-3903] - Improve support for interface return and parameter types for Json-B
  • [PAYARA-3913] - Instantiating wrappers - from 'new Wrapper(arg)' to 'Wrapper.valueOf(arg)' [Community Contribution: dvmarcilio]
  • [PAYARA-3914] - SonarQube - Replacing raw Collections EMPTY_... fields with generic methods empty…() [Community Contribution: dvmarcilio]
  • [PAYARA-3915] - SonarQube - Using Wrapper.parseWrapper() when converting String to primitive [Community Contribution: dvmarcilio]
  • [PAYARA-3916] - SonarQube - Optimizing String.lastIndexOf() for single char in appserver [Community Contribution: dvmarcilio]
  • [PAYARA-3917] - SonarQube - Optimizing String.lastIndexOf() for single char in nucleus [Community Contribution: dvmarcilio]
  • [PAYARA-3918] - Fixed typo in path [Community Contribution: johnmanko]
  • [PAYARA-3919] - SonarQube - Iterating on entrySet() instead of keySet() when key and value are needed [Community Contribution: dvmarcilio]
  • [PAYARA-3964] - Allow configuration of MDB bean pool size with ActivationConfigProperty
  • [PAYARA-3988] - Dynamic Docker Node Instances
  • [PAYARA-3990] - Support definition of tags for custom MicroProfile JMX vendor metrics
  • [PAYARA-4002] - Replace stats77 module with management-api
  • [PAYARA-4015] - Replace synchronised classes with unsynchronised in admingui/common-console [Community Contribution: svendiedrichsen]
  • [PAYARA-4034] - Cleanup of sonar warnings for common/amx-core
  • [PAYARA-4064] - Stabilize creation of default domain in build
  • [PAYARA-4065] - Reinitialize PayaraExecutorService on embedded server restart
  • [PAYARA-4073] - Use correct constructor of NotAuthorizedException in RolesAllowedRequestFilter

Security

Bug Fixes

  • [PAYARA-3101] - MicroProfile endpoints security support
  • [PAYARA-3698] - ! no longer allowed in admin password when using multimode asadmin
  • [PAYARA-3703] - update_file_user command fails when there are instances based on a different config.
  • [PAYARA-3736] - unsatisfied dependency HazelcastConfigSpecificConfiguration after migration from Payara 4 to 5 by backup and restore strategy
  • [PAYARA-3756] - High Memory Usage in Grizzly caused by large Object arrays remaining in memory
  • [PAYARA-3789] - DN representation of Client Certificate isn't uniform across Payara
  • [PAYARA-3797] - JDBC Connection Pool Flush when targeting Deployment Groups/Instances
  • [PAYARA-3815] - Support Remote Lookup of administered objects
  • [PAYARA-3822] - Some AMX metrics missing after server restart
  • [PAYARA-3860] - Race Condition When Starting Instance on JDK11 with Payara Server Full
  • [PAYARA-3875] - Update Docker Node Image Name
  • [PAYARA-3880] - Saving JVM Options corrupts the domain.xml
  • [PAYARA-3884] - Payara Micro adds JDK 11 warning when exploded application deployed
  • [PAYARA-3887] - Sonar issues sweep
  • [PAYARA-3895] - Check for if name is in use by deployment group is wrong
  • [PAYARA-3908] - JAX-RS Providers duplicated when CDI is enabled
  • [PAYARA-3909] - You can't use any of the variable types in JDBC connection pool settings
  • [PAYARA-3911] - Payara Server incorrectly detects Java version if it's different from the one used by the launcher [Community Contribution: vlumi]
  • [PAYARA-3922] - NamingException for certain situations when JAX-RS resource is defined as Stateless EJB.
  • [PAYARA-3931] - Revert the removal of 'java.ext.dirs' and 'java.endorsed.dirs` properties
  • [PAYARA-3968] - Payara Micro Postboot Script asadmin Commands Incorrect Quotation Mark Parsing
  • [PAYARA-3992] - JsonB serialization error when using Custom serializer
  • [PAYARA-3996] - Ensure that the TimerWrapper references correct EJBTimerService [Community Contribution: realityforge]
  • [PAYARA-4000] - A REST management DELETE command returns 415 code instead of 404
  • [PAYARA-4012] - Delete unused and unmaintained javaee-api modules
  • [PAYARA-4026] - MP Fault Tolerance fails on 2.0.1
  • [PAYARA-4028] - PostConstruct setting values are lost in Clustered Startup Singleton EJB within WAR/EAR
  • [PAYARA-4031] - Master Password synchronization inconsistencies across nodes
  • [PAYARA-4043] - Get rid of jvnet-parent
  • [[PAYARA-4044](https://github.com/payara/Payara...
Read more

Payara Platform 5.192

29 May 08:34
Compare
Choose a tag to compare

Notes

Domain.xml Changes

At long last, Payara Platform is shipping with support for JDK 11. It should be stressed that firstly: this support is in tech preview and secondly: if upgrading from an older version of Payara, you'll need to add some extra JVM options to your domain.xml configuration files. These are documented in the release documentation.

MicroProfile Changes

This release also brings our support of MicroProfile up to 2.2, providing updates to OpenAPI, Rest Client, and Fault Tolerance.

Docker Integration Changes

Finally, this release introduces the concept of a Docker node (also tech preview) as our first iteration of better native Docker integration. These function similarly to existing nodes, except the instances created for a Docker node are run within Docker containers.

Known Issues

  • [PAYARA-3865] - Output of asadmin osgi commands is not displayed. The issue was discovered later in release cycle. Workaround is to use OSGi shell over telnet. The server can be started by issuing command asadmin osgi telnetd start.

New Features

Improvements

  • [PAYARA-3385] - Allow OpenTracing @Traced to work with JAX-WS Web Services
  • [PAYARA-3386] - Complete login.conf configuration after creating custom security realm with default LoginModule configuration
  • [PAYARA-3417] - CertificateRealm should optionally return CN part a the certificate subject instead of the whole subject
  • [PAYARA-3419] - Persistent EJB Timer service forced too eagerly in cluster/Deployment group.
  • [PAYARA-3474] - Disable stacktrace logging when JPA schema generation tries to read from non existing sequence
  • [PAYARA-3688] - Make the timeout parameter configurable in the start-local-instance command
  • [PAYARA-3718] - Support System Properties with EJB over Rest
  • [PAYARA-3755] - Implement Full Support for JSON-B Serialization when using EJB Remote over HTTP
  • [PAYARA-3758] - Cleanup of sonar warnings for rest-service
  • [PAYARA-3781] - Community Contribution (edthorne): Allow wildcards when specifying interfaces for the data grid discovery mode
  • [PAYARA-3785] - Security small cleanup sweep 6
  • [PAYARA-3790] - CircuitBreaker with configuration file does not override the requestVolumeThreshold

Bug Fixes

  • [PAYARA-3162] - Endpoints defined within interface aren't picked up by MP openAPI
  • [PAYARA-3259] - Fix OpenAPI Context Creation
  • [PAYARA-3288] - Grizzly Memory Leak caused by HeapMemory and PooledMemory managers
  • [PAYARA-3444] - Warn when asadmin set targeting instances changes shared configuration
  • [PAYARA-3464] - Description does not save from MP config property in admin console
  • [PAYARA-3487] - Race condition in ConnectionPool
  • [PAYARA-3493] - Unable to Inject into EntityListener when using AttributeConverter
  • [PAYARA-3509] - additionalProperties of OpenAPI schema is not 'rendered'
  • [PAYARA-3515] - Fix setting authentication realm on Virtual Server with a property for default-web-module
  • [PAYARA-3521] - JAX-RS client with payara-embedded-all raises IllegalStateException for RequestTracingService run level
  • [PAYARA-3540] - Compile Error when Generating JavaDoc
  • [PAYARA-3541] - Error while deploying exploded war with payara micro
  • [PAYARA-3576] - embedded-all leaks upstream dependencies
  • [PAYARA-3660] - Payara Micro unable to inject MP RestClient instance in REST endpoint class
  • [PAYARA-3662] - context-root setting of glassfish-web.xml is ignored
  • [PAYARA-3665] - Asadmin Shell Only Reads a Single Input
  • [PAYARA-3666] - Fixes for issues found by tests for new health check as-admin commands
  • [PAYARA-3670] - "Rotation on Date Change" for Notification Logging is not applied on Admin Console
  • [PAYARA-3674] - CDI Async events not working on Payara Micro
  • [PAYARA-3682] - Error in gf-client manifest
  • [PAYARA-3686] - Default Principal can't be set from the Admin Console
  • [PAYARA-3692] - Class name is wrong or classpath is not set for : com.mysql.jdbc.jdbc2.optional.MysqlDataSource
  • [PAYARA-3696] - Payara Executor Service Error Printed when Application Client Container starts
  • [PAYARA-3702] - Community Fix (svendiedrichsen): NPE when Deploying an Application containing EJB Singletons
  • [PAYARA-3708] - Some INFO messages still printed by JLine in asadmin even with jline.log.disable=true
  • [PAYARA-3709] - Equals sign is added to system properties with empty value even if it's already in the key
  • [PAYARA-3723] - Community Fix (svendiedrichsen): Fix unclosed resources and potential NPE
  • [PAYARA-3729] - Jersey-media-json-jackson & jersey-hk2 Dependencies are not included with Ejb-Http-Client
  • [PAYARA-3738] - Community Fix (svendiedrichsen): Properly implement equals and hashcode method for OpenID state
  • [PAYARA-3753] - ClassCastException when using delayUnit Config Property
  • [PAYARA-3754] - @clustered Annotation Doesn't Use Bean Name
  • [PAYARA-3780] - Community Fix (aubi): Fix Http & Https ports in generated OpenAPI
  • [PAYARA-3783] - Community Fix (svendiedrichsen): Avoid using non-threadsafe XPath as static property
  • [PAYARA-3784] - OpenIdState equals method fixed
  • [PAYARA-3820] - Community Contribution (svendiedrichsen): Fixing sporadic NPE when archive has no JPA beans

Component Upgrades

Read more

Payara Platform 5.191

05 Mar 16:46
Compare
Choose a tag to compare

Release Highlights

A new year means a new version number for the Payara Platform. With the release of 5.191, we welcome the return of the Help Docs. Oracle recently donated GlassFish to the Eclipse Foundation along with the rest of Java EE, and that includes the help documentation. Thanks to their donation, we can use and update the help docs again for the Payara Platform.

As usual, our release continues our quest to eradicate all bugs, with this release bringing with it roughly forty fixes. Some of the notable bug fixes for this release include a fix for viewing remote instance monitoring information, some HTTP2 fixes (including a memory leak!), variable substitution not working for Payara Micro post-boot files, and making it so the interactive asadmin prompt doesn’t die when it prompts you for extra command parameters.

See below for a complete list of new features, improvements, security updates, and bug fixes:

New Feature

  • [PAYARA-1165] - Allow Payara Micro to set the context root with --contextRoot
  • [PAYARA-3132] - Incorporate Help Documentation back into Payara
  • [PAYARA-3169] - Thin Client Dependency for Remote EJB communications in client applications
  • [PAYARA-3261] - MicroProfile 2.1 (OpenTracing 1.3)
  • [PAYARA-3312] - Add Heartbeat into the Cluster Instance Descriptor
  • [PAYARA-3344] - Allow a configurable graceful behaviour for Payara Server's (and Micro) shutdown hook
  • [PAYARA-3381] - Daily rotation for Access Log
  • [PAYARA-3440] - New EJB Remoting Subsystem

Improvement

  • [PAYARA-546] - Allow setting SO_KEEPALIVE on the DAS or specific configs
  • [PAYARA-1896] - Refactor HealthCheck service commands to bring in to line with other asadmin commands
  • [PAYARA-2206] - Remove registration and installer modules
  • [PAYARA-2308] -- Community Contribution Replace StringBuffer with StringBuilder
  • [PAYARA-3262] - Don't create a new response in the JaxrsContainerExceptionMapper
  • [PAYARA-3306] - Starting asadmin with domain not running results in warning
  • [PAYARA-3310] - Make Service Name and Namespace Options for Kubernetes Cluster mode Optional
  • [PAYARA-3316] - Improve @AroundInvoke/@AroundTimeout interceptor handling
  • [PAYARA-3318] - Allow enabling or disabling HTTP methods for the j_security_check action
  • [PAYARA-3360] - asadmin list-commands only works when domain is running
  • [PAYARA-3382] - Make addDateStampToFirstAccessLogFile configurable
  • [PAYARA-3387] - Support reading Jax-ws catalog from WEB-INF
  • [PAYARA-3434] - Optimise FileArchive to reduce deployment times
  • [PAYARA-3438] - Improve usability of MP Health endpoint as readinessProbe for k8s
  • [PAYARA-3457] - Allow disabling auto-increment of Hazelcast port selection for the Domain Data Grid
  • [PAYARA-3458] - Improve Domain Data Grid Startup/Status Log Output
  • [PAYARA-3473] - Make Hazelcast initial wait time configurable
  • [PAYARA-3499] - Optimise ASClassLoaderUtil
  • [PAYARA-3505] - Prevent JLine Logging in Asadmin Multimode
  • [PAYARA-3507] - Improve the Executor Pool and Queue Sizes in Payara Micro
  • [PAYARA-3508] - Improve logging in ConnectionPool
  • [PAYARA-3514] - Community Contribution Typo and newline fix

Security

Bug

  • [PAYARA-2890] - Payara sometimes fails to load resources due to HTTP/2 server push
  • [PAYARA-2959] - Secured Remote EJBs (IIOP over SSL) not working in Payara 5
  • [PAYARA-3028] - Payara 5 Monitoring is broken for all instances apart from the DAS
  • [PAYARA-3031] - Fix HTTP/2 Trailer Issue
  • [PAYARA-3120] - TransactionScopedCDIEventHelperImpl Injection Error
  • [PAYARA-3160] - Minimum log file size error is ignored when set using logging.properties file
  • [PAYARA-3163] - WebAppClassLoader fails to find JAX-WS Handler class
  • [PAYARA-3164] - Variable substitution in post boot command file doesn't work in Payara Micro
  • [PAYARA-3219] - Move the Spanish localisation string file to the correct location
  • [PAYARA-3227] - JNDI Resources Can't Be Added to Deployment Group
  • [PAYARA-3257] - CDI Bean created (but fails) when interface has @path annotation
  • [PAYARA-3258] - Open API takes into account annotated interfaces without implementation
  • [PAYARA-3260] - Metrics API produces invalid metric names for Prometheus
  • [PAYARA-3319] - Felix gogo shell no longer works
  • [PAYARA-3328] - Increase the default thread pool and wait-queue size for the Payara Executor Service
  • [PAYARA-3348] - Resources and Properties Tabs have wrong name when viewing the Healthcheck Checker Tab
  • [PAYARA-3352] - If multiple invalid options are specified for asadmin only first is reported
  • [PAYARA-3356] - EJB Timer fails when using non-persistent flag
  • [PAYARA-3357] - asadmin shell issues when ask for additional data
  • [PAYARA-3358] - asadmin command stop-domains no longer works
  • [PAYARA-3362] - get-http-listener throws NPE
  • [PAYARA-3366] - Payara MP Config getConverters() is not thread-safe
  • [PAYARA-3367] - Strange CDI BeanManager behavior when creating interceptor instance on domain restart
  • [PAYARA-3373] - Certificate realms with a custom JCE provider still raise exceptions
  • [PAYARA-3376] - Some JVM parameters are not correctly stored through the Web Admin Console
  • [PAYARA-3384] - Possible infinitive loop
  • [PAYARA-3424] - @clustered Singleton not working in EAR assembly
  • [PAYARA-3425] - asadmin recorder generates wrong command for create-network-listener
  • [PAYARA-3432] - Setting core-pool-size of ExecutorService result in NPE
  • [PAYARA-3443] - Allow SL4FJ to redirect all JUL statements to Logback in Payara Micro (Fix HV error)
  • [PAYARA-3449] - list-protocol-filters command fails with NPE
  • [PAYARA-3451] - Managed Scheduled Executor Service doesn't execute tasks from versioned applications
  • [PAYARA-3452] - Memory Leak with http2 enabled on Payara 5.184 and latest glassfish
  • [PAYARA-3463] - Unable to retrieve JVM options through Rest admin endpoint
  • [PAYARA-3478] - SO_KEEPALIVE checks for wrong port, and Enable Logic is Wrong
  • [PAYARA-3494] - Payara 5.184: PersistentEJBTimerService not serializable
  • [PAYARA-3511] - ClassCastException when using CircuitBreaker.delayUnit Config Property
  • [PAYARA-3512] - CircuitBreaker Interceptor Checks for Config Override on Wrong Annotation
  • [PAYARA-3520] - Mojarra Prints Debug Messa...
Read more