Fixed Issues
This section details the issues marked as bugs that have been fixed for this release.
Payara Fixes
This section details the fixes implemented by the Payara team or community.
• 270 - Support rolling updates
• 300 - Bean identifier index inconsistency after Hot re-deployment from NetBeans
• 385/PAYARA-444/GLASSFISH-21371 - Alternate descriptors not persisted in remote deployments
• 415/PAYARA-405 – It is possible to set invalid ejb container thread pool settings
• 418/PAYARA-415 - Can not inject PayaraMicroRuntime CDI bean when deploying a war on the PayaraMicro command line
• 420 - Changed the way to load payara-bootstrap.properties.
• 423 - Payara Micro name not passed through to the instance descriptor
• 427/PAYARA-322 - enable-secure-admin-principal adds principal multiple times
• 433 - Clustered / Versioned applications cannot be enabled on individual cluster instances
• 458/PAYARA-466 - File deleted after successfuly deployed with web gui local file dialog
• 460/PAYARA-459 - ${com.sun.aas.hostName} not resolved correctly in JVM options
• 467/PAYARA-457 - classloader work
• 472/PAYARA-454 - NPE thrown by JMS Ping if no Default JMS Host is configured on the DAS
Upstream Fixes
This section details the fixes brought in from the GlassFish upstream.
• GLASSFISH-21172 - javax.transaction.RollbackException from @Transactional bean has no cause set
• GLASSFISH-21426 - Application deployment fails when DataSourceDefinition annotation is used within an EJB inside a war.
Known Issues
Known issues can be seen on our GitHub issues page here: https://github.com/payara/Payara/issues
Add Comment
Comments
Please sign in to leave a comment.