Releases: payara/Payara
Releases · payara/Payara
Payara Server 4.1.1.161
Release Highlights
The most eye catching feature in this release is a new look for the Admin Console; we’ve given the Admin Console another go over from our initial attempt, rebranding it to look more distinctly Payara!
The more exciting highlight of this release is the Healthcheck Service. In its initial release, this service allows you to monitor CPU usage, the number of times Garbage Collection has occurred, the machine memory usage, the heap memory usage, and any hogging threads.
Documentation for it can be found here, and documentation for the asadmin commands can be found here.
Updated Modules
This section details the modules that have been updated since the last release (4.1.1.154).
- Jersey 2.22.1
- EclipseLink 2.6.2 (Patched to payara-p1)
- GlassFish Corba 4.0.1 (Patched to payara-p3)
- Woodstock 4.0.2.10 (Patched to payara-p2)
- Metro 2.3.2-b608 (Patched to payara-p2)
- MQ 5.1.1-b02 (Patched to payara-p1)
- Apache commons-fileupload 1.3.1
Enhancements
This section details the issues marked as enhancements that have been implemented for this release.
- 511 – Add support for Informix for persisted ejb timers
- 512 – Update usages of EclipseLink
- 551/PAYARA-527 - Speed up Payara Micro boot times
- 566/PAYARA-540 - Removed cause of spurious warning RAR875
- 570/PAYARA-491 - Redesign of the admin console
- 572/PAYARA-408 - Option to turn on orb keepalive
- 576/PAYARA-549 - Currently only deployment artifacts ending in .war are deployed
- 583/PAYARA-458 – Many threadpools have bad names
- 586/PAYARA-554 – SQL tracing and slow SQL logging
- 588 – Payara Micro can’t be stopped and restarted in the same process
- 593/PAYARA-359 - JBatch supports SQL server
- 605/PAYARA-518 – Disable SSL3 on Sec-Admin-listener
- 613/PAYARA-558 – Editing the front page
- 619/PAYARA-488 – Restart behaviour when running windows service
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.
- 195/PAYARA-222 – Jbatch and Postgresql db as job repository fails
- 229/PAYARA-548 - Fix CDI and SAM
- 468/PAYARA-323 – Admingui crashes after timeout
- 481/PAYARA-477 – Behaviour of Logging for @Transactional CDI methods
- 491/PAYARA-346 – WELD warnings during deployment
- 492/PAYARA-511 – Redploying war/ear on cluster fails
- 494/PAYARA-376 – Instance server.log written to despite change of log file name/location
- 497/PAYARA-490 – admin GUI interface refresh issue
- 500/PAYARA-406 – Wrong thread name in server.log
- 502 - Message catalog key not transformed: using.default.ds
- 505/PAYARA-510 – Payara does NOT rollback when RuntimeException occurs in CDI @Transactional method using JDBC
- 510/PAYARA-547 - @DataSourceDefinition defined data source can't be used in persistence.xml
- 525/PAYARA-449 – Sporadic “attempted duplicate class definition for name” in Payara 4.1.153
- 534/PAYARA-446 – Multiple cookies cannot be added using Headers.putAll()
- 535/PAYARA-526 - Problems with jndi lookup
- 536/PAYARA-551 - Websocket @OnOpen sometimes isn't called
- 539/PAYARA-556 - ACC needs 3 seconds for initialContext.lookup("myHome")
- 540/PAYARA-520 – Fix Batch: SQL string is not Query
- 545/PAYARA-492 – Fix WSIT enabled WS services
- 549/PAYARA-480 - Warnings when connecting via JMX
- 555/PAYARA-529 - Problem with mcAddress on payara micro
- 556/PAYARA-496 - ensure the truststore is only written to when we have read/write permissions
- 560/PAYARA-533 - Upgrade Commons File Upload
- 561/PAYARA-486 - Fixed wrong session count after failover
- 564/PAYARA-538 - Upstream commit breaks redeploy of CargoTracker
- 567/PAYARA-371 - Spurious warning when changing open mq admin/guest password
- 578/PAYARA-346 - added javax.ejb as an imported package to the weld integration bundle
- 589/PAYARA-557 - Incorrect Server Version and Vendor provided in JMX Bean
- 596/PAYARA-568 - Payara Blue uses incorrect key algorithm
- 603/PAYARA-560 – Not all batch objects use prefix/suffix
- 615/PAYARA-495 - Fix FileNotFoundException "noop=true"
- 618 – Deployment of EJB_Timer_App when app has orm.xml
- 627 – Webservice deployed from directory archive on windows fails
- 632/PAYARA-602 - Update woodstock version to fix exploit
Known Issues
Known issues can be seen on our GitHub issues page here: https://github.com/payara/Payara/issues
Payara Server 4.1.1.154
Release Highlights
This release brings us back in line with GlassFish 4.1.1, with the benefit of all our additional fixes and enhancements from our previous releases, as well as a few more. Of particular interest in this release:
- Up to date with GlassFish 4.1.1.
- Removal of the dependency on .NET Framework 3.5, allowing Payara to be used with .NET Framework 4.
- The payaradomain domain will now use an embedded Derby database for its default datasources (domain1 is unchanged to retain drop-in replacement viability).
- You can now set DISABLED as a JMS Broker type, allowing you to disable the OpenMQ Broker.
- Setting size-based log rotation to 0 will now turn it off.
In line with our naming strategy, our version number has also been extended for this release to reflect the fact that we are up to date with GlassFish 4.1.1.
Updated Modules
This section details the modules that have been updated since the last release (4.1.153).
- Mojarra 2.2.12
- Webservices 2.3.2-b608
- JAXB 2.2.12-b141219.1637
- JAXB-API 2.2.13-b141020.1521
- Weld 2.2.16.Final
- Tyrus 1.11
- JBatch 1.0.1-b09
- Grizzly 2.3.23
- HK2 2.4.0-b32
- Jersey 2.22
- Hazelcast 3.5.2
Enhancements
This section details the issues marked as enhancements that have been implemented for this release.
- 414/PAYARA-389 - Disable size based log rotation when set to zero
- 421/PAYARA-447 – Add some simple asadmin commands
- 425 - Make Instance Descriptor null safe when zero applications deployed
- 429/PAYARA-387 - Make the default DerbyPool use Derby Embedded
- 439/PAYARA-427 - Allow DISABLED as a JMS Broker type.
- 440 - Allow MDB to specify the resource adapter to use in the Activation Config
- 457/PAYARA-409 – Remove Update Center
- 463/PAYARA-369 - Payara product names are not correct in the console. Should be Payara Server
- 467/PAYARA-457 - classloader work
- 475/PAYARA-347 - Converter autoApply does not work for primitive types
- 479/PAYARA-453 - Windows service wrapper depends on .NET Framework 3.5
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
- 327 - Tyrus send partial message more than buffer size will cause exception in catalina OutputBuffer
- 350 - Using AJP when downloading of large streaming data results in the errors "OutOfMemoryError: Java heap space" and "503 Service Temporarily Unavailable"
- 371 - Creating an HTTP listener with security enabled using web admin console doesn't work
- 377 - JAX-RS integration with EJB Technology doesn't work
- 385/PAYARA-444/GLASSFISH-21371 - Alternate descriptors not persisted in remote deployments
- 395 - IllegalArgumentException when starting a payara micro on Windows via cli with --rootDir or --domainConfig
- 409/PAYARA-266 - Unable to add or remove java debug option using asadmin
- 410/PAYARA-349 - Batch configuration requires data source on DAS
- 411/PAYARA-372 - JMS broker issues when broker port is already in use
- 412/PAYARA-373 - REST interface to create auth-realm fails
- 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/PAYARA-452 - 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
- 465/PAYARA-448 - Could not load class javax.rmi.CORBA.EnumDesc
- 472/PAYARA-454 - NPE thrown by JMS Ping if no Default JMS Host is configured on the DAS
- 485/PAYARA-388 - Server log displays webappClassLoader severe warnings on shutdown
- PAYARA-370 - Fixes confusing typo in the admin console
- GLASSFISH-21007 - HTTP Upgrade handler init called twice when access log is turned on
Upstream Fixes
This section details the fixes brought in from the GlassFish upstream.
- GLASSFISH-21009 - The behavior of --timeout-seconds is not in line with the document
- GLASSFISH-21172 - javax.transaction.RollbackException from @Transactional bean has no cause set
- GLASSFISH-21381 - war with web service not deploying correctly
- GLASSFISH-21391 - Disable SSLv3 by default in config module
- GLASSFISH-21426 - Application deployment fails when DataSourceDefinition annotation is used within an EJB inside a war.
- fix enforcer version of the javadoc-jdk8+ profile activation
- fixed redundant null check caught by findbugs for an earlier commit
- In case of JDK 9, java.logging loading sun.util.logging.resources.logging resource bundle and java.logging module is used as the cache key with null class loader.So we are adding a null check
- As per servlet spec 3.1, when Request.setCharacterEncoding(String enc) is called, the call should be a no-op if request input parameters have already been read or if getReader() has been called. However, at present, check is there only in case of use of reader and no check if parameter has been read by a different method call (e.g by calling getParameter()). This seems to be a regression introduced during Grizzly 2.0 integration in revision 46674. Changes have been made to check if parameters have been processed/read too. character encoding will not be set if either parameters have been reader or reader is being used.
- EjbDescriptor abstract class implements JndiNameEnvironment and WritableJndiNameEnvironment. For some of these methods, though there is a generic implementation (For example via CommonResourceDescriptor), these methods still needs to be implemented in a specific way within EjbDescriptor abstract class to get the expected behavior whenever these methods are invoked in EjbDescriptor's context. To ensure the same, a new unit test is being introduced within source workspace, namely EjbDescriptorInheritedMethodImplementationTest,which basically ensures following two things: All methods defined in JndiNameEnvironment and WritableJndiNameEnvironment have a direct implementation within EjbDescriptor abstract class and all these methods are marked final in EjbDescriptor to ensure that sub-classes of EjbDescriptor don't override these methods accidentally, possibly causing unexpected behavior.
- fix web container issue filed in Grizzly
Known Issues
Known issues can be seen on our GitHub issues page here: https://github.com/payara/Payara/issues
Payara Server 4.1.153
Release Highlights
This release has several notable features:
- The Payara Micro API has been improved, now granting control over running instances and the ability to run asadmin commands.
- There is now an auto-binding feature for the HTTP and HTTPS ports of Payara Micro instances. This feature allows Payara Micro instances to automatically find a free port if the default or specified HTTP or HTTPS ports are already bound to.
- This release also introduces the Payara-Blue series of distributions, built using the IBM JDK for AIX systems.
See the What's new in Payara 4.1.153 blog for descriptions of these features.
Updated Modules
This section details the modules that have been updated since the last release (4.1.151).
- Mojarra 2.2.11
- Javax XML Registry API 1.0.7
- Weld 2.2.13.Final
- JBatch Container 1.0.1-b08
- JBatch SPI 1.0.1-b08
- Grizzly 2.3.21
- Jersey 2.19
- Jackson 2.5.1
- Mail 1.5.4
- Hazelcast 3.5
Enhancements
This section details the GitHub issues marked as enhancements that have been implemented for this release.
- 61 - Docker support?
- 175 - Add extra usage instructions for set-batch-runtime-configuration Asadmin command
- 188 - CDI container should be able to inject Cache
- 297 - Make Payara Micro Failfast
- 314 - Extend Payara Micro api to enable deployment from an InputStream
- 321 - Support all attribute names in set-log-attributes
- 325 - Jcache enhancements
- 332 - Review file handling for Master Password
- 333 - file permissions should be set on master-password file using NIO2 file attribute api rather than chmod-via-ProcessBuilder
- 334 - file permissions should be set on glassfish client password file using NIO2 file attribute api rather than chmod-via-ProcessBuilder
- 339 - Upgrade to Hazelcast 3.5 for JCache fix
- 347 - Payara micro enhancements
- 349 - Don't make me think about payaradomain vs. domain1 (have
asadmin start-domain"just work") - 359 - Automatically increment busy payara micro http and https ports
- 361 - Update Japanese translation
Fixed Issues
This section details the GitHub issues marked as bugs that have been fixed for this release.
- 204 - JBatch fails to execute job on @Startup
- 276 - lib/ext does not exist in domains created by 4.1.152 resulting in failure during add-library
- 288 - payara embedded/micro artifacts unresolvable in maven central repo
- 291 - Fix of domainConfig argument, the index specified error.
- 293 - Fix Payara Micro Warnings on boot
- 329 - Add support for access-logging of session attributes
- 330 - glassfish-ha module uses incorrect groupId for ha-hazelcast-store dependency
Upstream Fixes
This section details the fixes brought in from the GlassFish upstream.
- Fix for GLASSFISH-20856
- fix for bug GLASSFISH-20864
- Glassfish part of the fix of the https://java.net/jira/browse/GRIZZLY-1786
- GLASSFISH-21131 fix
- fix aggregated test report for newer hudson versions
- Fix for GLASSFISH-21366
- Changed fix for GF 20680326
- fix broken images links, and allow jdk8 to be used to have the {@docRoot}
- FindBug fix
- fix for bug-20864
- fix for GLASSFISH-21261
- Fix for GLASSFISH-20932
- fiix for bug-20931
- Fix for GLASSFISH-21343 - GlassFish fails to start on MacOSX 10.10.3
- Fix for findbug GF_UNCONDITIONAL_DEBUG_LOGGING error in In stalledLibrariesResolver.java
- Fix for findbug DLS_DEAD_LOCAL_STORE error in WebContainer.java
- fix no args usage of gfbuild.sh
- Fix for GLASSFISH-21251
- Fix for GLASSFISH-20842 - X-Forwarded-Proto not honored by glassfish 4.0
- Commit for Bug GLASSFISH-21028:Deployment from Web Console: temporary files are not deleted
Payara Server 4.1.152
Release Highlights
The payara-embedded-nucleus distribution has been replaced by the Payara Micro distribution. This is a light-weight distribution that has Hazelcast integrated to allow for automatic web session clustering and JCache distribution.
We have also added a separate Payara domain template, which has a few optimisations:
- Increased PermGen Size of 512m (previously 192m)
- Increased Xmx value of 1024m (previously 512m)
- Removed Felix OSGI parameters
- Increased HTTP thread pool size of 50 (previously 5)
- Changed the JVM option –client to –server (this has been done for both domain templates)
- Added the JVM option to reject client initiated TLS renegotiation
Updated Modules
This section details the modules that have been updated since the last release (4.1.151).
- Hazelcast 3.4.2
- EclipseLink 2.6 (Payara Patched)
- Weld 2.10.SP1
- GlassFish-CORBA 4.0.1-p1 (Payara Patched)
- Grizzly 2.3.19
- HK2 2.4.0-b12
- HK2 Plugin 2.4.0-12
- Jersey 2.17
- JMS API 2.0.1
- Mojarra 2.2.10
- Webservices 2.3.1-b419 (downgrade)
- JAXB API 2.2.12-b140109.1041 (downgrade)
- JAXB 2.2.10-b140802.1033 (downgrade)
- MQ 5.1.1-b02
- Tyrus 1.10
- Shoal 1.7.0-M1 (Payara Patched)
Enhancements
This section details the GitHub issues marked as enhancements that have been implemented for this release.
- 72 – Create fix for GLASSFISH-21236 (JDK 9 Support)
- 154 - Payara #154 - Removed the Classloader hack for older Hazelcast versions
- 166 – Upgrade EclipseLink to the latest
- 168 – Update the default-web.xml to to set “xpoweredBy” init param to false for JspServlet
- 186 – Within Netbeans, I no longer can create a glassfish server entry with payara-4.1.155
- 190 - Adds cluster back into payara-minimal
- 193 - Add hazelcast dependency to payara-web-embedded pom
- 206 - Review table names for Jbatch
- 208 – Get Web Session Clustering on Payara Embedded
- 217 – Upgrade Mojorra to 2.2.10
- 230 – Add Serialization of values in JSR107 CDI
- 234 – Upgrade Weld to 2.2.10.Final or newer
- 259 - Ensure key system properties are set by Payara Micro
Fixed Issues
This section details the GitHub issues marked as bugs that have been fixed for this release.
- 138 – Verify Symbolic link checking in Payara
- 139 – Fix exception handling code in com.sun.enterprise.util.io.FileUtils.java
- 191 – Payara Embedded Web Profile does not contain Hazelcast
- 192 – Prevent null pointer exception when GMS is not enabled
- 197 – Slow startup/hang when application uses Eclipselink and genericra
- 207 – Fix checking to verify table existence in specified schema in DB2 persistence manager
- 209 - CDI Injection in Entity Listener results in null reference
- 218 - EJB webservice with wssecurity policy gets NoClassDefFoundError: org/apache/commons/logging/LogFactory
- 216 – com.sun.gjc.spi.jdbc40.ProfiledConnectionWrapper40 changes Exception thrown by wrapped jdbc Connection (fix inside)
- 228 – Investigate GLASSFISH-20670 JSF Performance
- 239 - java.lang.ClassNotFoundException: javax.xml.parsers.ParserConfigurationException not found by org.eclipse.persistence.moxy
- 244 – Transaction is aborted after 2 minutes
- 251 - Performance regression in corba serialization in migration glassfish 4.0 -> payara-4.1.151
- 262 - Incorporate fix for GLASSFISH-21343
- 269 – Nightly build 2015-04-28 does not allow creating jdbc connection pool resources through web interface
Payara Server 4.1.151
Release Highlights
JBatch has been upgraded to version 1.0.1-b04 and now recognises MySQL, Postgresql, Oracle, and DB2 as persistence managers. Hazelcast 3.4 has also been implemented as a clustered web session store and provider of JSR107.
We are also now providing distributions of the Multi-Language (ml) releases, which contain the l10n packages from GlassFish.
Note – We lack translations for the additions we have made, such as the Hazelcast configuration page in the Admin Console. We would prefer to not accept internet translations as they are typically inaccurate.
Updated Modules
This section details the modules that have been upgraded since the last release (4.1.144).
- Jersey 2.15
- Tyrus 1.9
- JSTL-Impl 1.2.4
- Mojarra 2.2.9
- Weld 2.2.7
- Javax Batch API 1.0.1-b01
- JBatch Container 1.0.1-b04
- JBatch SPI 1.0.1-b04
- Grizzly 2.3.18
- HK2 2.4.0-b08
- HK2 Plugin 2.4.0-b08
- Jackson 2.5.0
- Jettison 1.3.7
- Shoal 1.6.22
- Metro – 2.3.2-b608
- JAXB-API – 2.2.13-b141020.1521
- JAXB – 2.2.12-b141219.1637
New Module
- Hazelcast 3.4
Enhancements
This section details the GitHub issues marked as enhancements that have been implemented for this release. You can view the issues in detail by following the provided links.
- 25 – Disable SSLv3 in default domain template
- 28 – Integrate Hazelcast as JSR107 provider
- 29 – Integrate Hazelcast as a clustered web session store
- 80 – Integrate MySQL persistence manager into JBatch
- 81 – Integrate Oracle persistence manager into JBatch
- 82 – Integrate PostgreSQL persistence manager into JBatch
- 83 – Integrate DB2 persistence manager into JBatch
- 86 – Integrate different persistence managers into GF-batch-connector
- 111 – Allow Blank Schema for JBatch
- 149 – Update underlying specification implementations
Fixed Issues
This section details the GitHub issues marked as bugs that have been fixed for this release. You can view the issues in detail by following the provided links. - 45 – Glassfish 21148 - fixed bug in SSO clustered session management
- 46 – Glassfish 21219
- 47 – GLASSFISH-21146 Fixed NPE in log
- 53 – Merge Patched Grizzly jar into build
- 68 – Merge Fix for GLASSFISH-21251
- 70 – Merge Fix for GLASSFISH-21007
- 76 – Upgrade Weld to 2.2.4.Final or newer
- 79 – Merge fix for GLASSFISH-21261
- 84 – Fix XForwarded-Proto GLASSFISH-20842
- 85 - Create Fix for https://java.net/jira/browse/GLASSFISH-21249
- 101 – Force early creation of static transaction manager to fix GLASSFISH-21175
- 114 – Fix GLASSFISH-21265
- 120 – Fix GLASSFISH-20994
- 122 – JDBC Monitoring MBeans not working in JConsole
- 127 – Further MBeans are broken GLASSFISH-21276
- 131 – Java EE 7 Sample Chunk CSV Database Test Fails
- 141 – Fix GLASSFISH-21017
- 180 – Fix GLASSFISH-21125
Payara Server 4.1.144
Release of Payara Server 4.1.144 built from GlassFish upstream 4.1.
Downloads of Web Profile and Payara Minimal are available at http://www.payara.co.uk/downloads