Fixed Issues
This section details the issues marked as bugs that have been fixed for this release.
Bug Fixes
- [PAYARA-1679] - Deploying to the DAS fails when there are multiple clusters available
- [PAYARA-1904] - The get/set-config-ordinal asadmin command does not accept JNDI as a valid source
- [PAYARA-1907] - CDI Weld probe activated causes exceptions with stateless EJBs
- [PAYARA-1922] - Incorrect file structure when packaging a custom glasfish-acc.xml file with the package-appclient utility script
- [PAYARA-1924] - Some notifiers throw a null pointer exception when execution options are unset
- [PAYARA-1950] - Versioned applications break deployment of other applications
- [PAYARA-1960] - Fix CORBA thread pool issues
- [PAYARA-1966] - Problem when initialising Timer Store on Payara Micro 173 with --noCluster
- [PAYARA-1968] - Small visual issue in the Batch Admin UI
- [PAYARA-1997] - NPE on asadmin list-batch-job-executions
- [PAYARA-2001] - Fix time help label on JMX Monitoring
- [PAYARA-2005] - Improper message from start-domain
- [PAYARA-2006] - The value of "Group List" in "Realm User" cannot be deleted
- [PAYARA-2008] - CPU Healthcheck percentage wrong
- [PAYARA-2010] - The connection pool checker is broken and prevents server from starting if configuration exists
- [PAYARA-2013] - The number of times EJB create method is called is incorrect in JConsole
- [PAYARA-2015] - Threads on remote applications (appclient) using the ORB do not gracefully shut down
- [PAYARA-2019] - CDI Weld probe activated causes NPE in FilterDefDecorator for Async Request
- [PAYARA-2021] - CDI Dev Mode UI is broken in the Admin Console
- [PAYARA-2025] - CDI Dev Mode checkbox is enabled by default
- [PAYARA-2050] - Fix second NPE from versioned applications
Known Issues
Known issues can be seen on our GitHub issues page here: https://github.com/payara/Payara/issues
Add Comment
Comments
Article is closed for comments.