Payara Server 4.1.2.174 Release Notes
Release Highlights
This release has been based on GlassFish Server Open Source 4.1.2 which was released on March 31, 2017.
Bugs & Fixes
-
PAYARA-1679 - Deploying to DAS fails when there are multiple clusters available
-
PAYARA-1840 - RAR file loading fails from Uberjar when there’s no ra.xml
-
PAYARA-1904 - The get/set-config-ordinal asadmin command does not accept JNDI as a valid source
-
PAYARA-1906 - JAX-RS resources are displayed as JSP in the Admin Console
-
PAYARA-1907 - CDI Weld probe activated causes exceptions with stateless EJBs
-
PAYARA-1919 - asadmin recorder tab has incorrect highlighting
-
PAYARA-1924 - Some notifiers through a NPE in handleNotification and not configured
-
PAYARA-1949 - Stop JMX monitoring plugin from being packaged with micro
-
PAYARA-1950 - Versioned applications break deployment of other applications
-
PAYARA-1951 - Refactor usage of deprecated addAnnotatedType method from BeforeBeanDiscovery
-
PAYARA-1952 - Payara Embedded throws a NoClassDefFoundError on startup
-
PAYARA-1957 - Post boot commands parser errors out with speech marks
-
PAYARA-1962 - Hazelcast Serializer Configuration possibly mistakenly is overridden
-
PAYARA-1966 - Problem when initialising Timer Store’ on Payara Micro 173 with –noCluster
-
PAYARA-1988 - JDBC Connection Pooling - monitoring values can become negative
-
PAYARA-1991 - Micro instances send the name instead of the instance UUID
-
PAYARA-1992 - JMX monitoring data collection not stops and send data with weird frequency
-
PAYARA-1997 - BATCH CLI: NPE on asadmin list-batch-job-executions
-
PAYARA-2003 - Payara ignores variables in asenv.conf that begin with the letter ``S''
-
PAYARA-2005 - Improper message from start-domain -debug mode
-
PAYARA-2006 - The value of
Group List'' inRealm User'' cannot be deleted -
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-2029 - Possible NPE in the get-rest-monitoring-configuration command
-
PAYARA-2037 - Variable substitution isn’t performed in persistence.xml for Properties
-
PAYARA-2040 - JMS physical destination config true/false values incorrectly fetched
-
PAYARA-2047 - CDI Beans annotated with @Traced aren’t traced
-
PAYARA-2053 - update-connector-security-map cannot change user-groups to principals and vice versa
-
PAYARA-2056 - NPE at PoolManagerImpl.handleLazilyAssociatedConnectionPools()
-
PAYARA-2060 - HealthCheck service logs WARNING on every CDI event bus event received
-
PAYARA-2065 - Web-service endpoint is not available for the deployed EJB application
-
PAYARA-2074 - Handle log messages in MessageFormat by escaping double single quote
-
PAYARA-2075 - asadmin set command throws NPE on beans with readonly properties
-
PAYARA-2086 - Secure Client-Initiated Renegotiation cannot be disabled
-
PAYARA-2110 - Default TimerPool resource absent in cluster-config
-
PAYARA-2115 - Direct String references to AS-WEB-GLUE- or AS-WEB-CORE- LogFacade.java
-
PAYARA-2124 - update-connector-security-map can’t delete backend principal password
-
PAYARA-2126 - DataSource returns null connection when obtained from JNDI lookup
-
PAYARA-2127 - asadmin subcommand output CLI031 warning message
-
PAYARA-2128 - A thread pool with a special character cannot be deleted
-
PAYARA-2129 - Web container still does not call AsyncContext.complete() on timeout/exception
-
PAYARA-2132 - Deleting JMS Physical Destinations results in a 404 error
-
PAYARA-2145 - SessionContext.getCallerPrincipal() returns previous principal on TimerService
-
PAYARA-2155 - Directory traversal exposes file system resources
-
PAYARA-2158 - IllegalArgumentException when configuring the connector security map
-
PAYARA-2159 - Unable to Save in ``Edit Connector Connection Pool Security Map'' in Admin GUI
-
PAYARA-2166 - Deploy without checking the database fails when deploying a Persistence Unit
-
PAYARA-2167 - Honour default-context-path in web.xml in case of an ear
-
PAYARA-2168 - Race condition in ConnectionPool (connectors-runtime)
-
PAYARA-2178 - Micro postboot commands should skip empty lines
-
PAYARA-2191 - Configuring the HealthCheck Notifiers for a Standalone/Cluster instance targets DAS
-
PAYARA-2192 - Configuring the JMX Monitoring Notifiers for a Standalone/Cluster instance targets DAS
-
PAYARA-2195 - Add log message in server.log when skipping resource validation
-
PAYARA-2197 - scanXmlDefinedClasses in webFragment application
-
PAYARA-2198 - No confirmation message is displayed on Enable/Disable action
-
PAYARA-2199 - Can’t create Connector Connection Pool for inbound RA deployed on a cluster
-
PAYARA-2200 - Intermittent failure on nonBlockingInputWithAsyncDispatch
-
PAYARA-2210 - Async listener onTimeout calling complete causes NPE
-
PAYARA-2215 - Payara Micro start parameter –addjars not working on windows
-
PAYARA-2238 - Request Tracing Runtime Exception in Admin Console
-
PAYARA-2240 - JMX Monitoring values with spaces can now be escaped instead of breaking
-
PAYARA-2255 - Fix intermittent start-up issues with Payara 173
Improvements
-
PAYARA-1744 - Add support for environment variables to the pre and post boot commands
-
PAYARA-1843 - Improve descriptive text on the JMX Monitoring config
-
PAYARA-1894 - Add Deployment Date/Time alongside Deployment Time in the admin console
-
PAYARA-1902 - Historic request races should display human-readable date
-
PAYARA-1953 - Admin console integration for notifiers with JMX monitoring
-
PAYARA-1958 - Set all dependency versions within the pom to use the $\{artifactId.version} pattern
-
PAYARA-1961 - Refactor payara-fang to rest-monitoring-service
-
PAYARA-1994 - Change Payara Micro –addJars command to –addLibs
-
PAYARA-2039 - Update Microprofile Config implementation to 1.1
-
PAYARA-2125 - Replace hardcoded versions with maven properties
-
PAYARA-2174 - Option to prefer module name specified in ejb-jar.xml over the name argument to deploy
-
PAYARA-2248 - Disable notifier service by default in Payara Micro
-
PAYARA-2249 - Phone Home should not update domain.xml in Payara Micro
-
PAYARA-2250 - Remove MEJB service from Micro as it wastes boot time
Security Fixes
-
PAYARA-2109 - Protect Admin Console Web Pages against Clickjacking/UI Redress attacks
-
PAYARA-2151 - Backport fix for CVE-2017-12615 in Tomcat Code Base
-
PAYARA-2152 - Confirm Payara is unaffected by CVE-2017-12616
Known Issues
Known issues can be seen on our GitHub issues page here: https://github.com/payara/Payara/issues.