Payara Server 4.1.1.161 发布，更新如下：

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

下载页面：Payara Server 4.1.1.161