Payara Server 4.1.1.171

Bugs

• [PAYARA-737] - Resolve GLASSFISH-21532 GlobalTID breaks the equals/hashCode contract
• [PAYARA-934] - aliased password cannot be replaced by the value of the alias
• [PAYARA-995] - AS-WEB-CORE-00369 errors when using Hazelcast for session replication
• [PAYARA-1052] - MicroProfile UberJAR startup Grizzly error
• [PAYARA-1082] - Authorization stops working after app redeploy
• [PAYARA-1115] - Parameterised log messages are incorrectly escaped
• [PAYARA-1185] - JMS Service Binding Address not working correctly for application client
• [PAYARA-1188] - Negative Values for CountOpenConnections
• [PAYARA-1195] - Unable to deploy activemq-rar resource under Payara 4.1.1.164
• [PAYARA-1205] - Fix for PAYARA-1036 breaks Microprofile
• [PAYARA-1219] - Jersey EncodingFilter does not work in Payara 4.1.1.164
• [PAYARA-1223] - WELD-000163: Non-unique bean deployment identifier detected
• [PAYARA-1224] - Concurrency bug in SessionStatsProvider
• [PAYARA-1244] - Default role mapping setting broke the domain level setting
• [PAYARA-1254] - Spurious warning: "Severe: Unknow type constant pool 15 at position xxx"
• [PAYARA-1259] - Sending access logs to the console does not work as expected
• [PAYARA-1261] - Fix Warning: Context path from ServletContext: differs from path from bundle: /
• [PAYARA-1277] - Could not deploy simple war on cluster while Internet is off
• [PAYARA-1281] - Setting "Slow Query Log Threshold" to a positive value other than 1 causes password errors
• [PAYARA-1282] - JMX Monitoring service with dynamic=true will not be enabled unless the server is restarted
• [PAYARA-1283] - JMX monitoring service adding properties does not fail gracefully
• [PAYARA-1290] - JNDI conflict with local data sources
• [PAYARA-1380] - Fix session load NPE
• [PAYARA-1396] - Felix OSGi Web Console fails when installed

New Features

• [PAYARA-698] - Email Notifier
• [PAYARA-700] - JMS Notifier
• [PAYARA-701] - SNMP Notifier
• [PAYARA-702] - XMPP Notifier
• [PAYARA-703] - HipChat Notifier
• [PAYARA-704] - Slack Notifier
• [PAYARA-705] - Payara Micro (CDI Event Bus) Notifier
• [PAYARA-822] - Add simple API for registering a SAM
• [PAYARA-1039] – Public API JAR
• [PAYARA-1053] - Add a way to run asadmin commands against Payara Micro
• [PAYARA-1065] - Add controls for EJB pool size per EJB
• [PAYARA-1122] – Historical Request Traces
• [PAYARA-1125] – Historical Healthcheck entries
• [PAYARA-1138] - Extreme Classloader Isolation
• [PAYARA-1141] - Enable the DAS to send asadmin commands to Micro cluster members
• [PAYARA-1143] - Add support for CDI event bus into Payara Server
• [PAYARA-1383] - Admin Console integration for Health Check Service
• [PAYARA-1386] - Add support for substituting environment variables in domain.xml

Improvements

• [PAYARA-895] - Create new JAR format for microprofile
• [PAYARA-1044] - Payara Micro: Refresh logging configuration after set-log-levels
• [PAYARA-1048] - Payara Micro command line options should be case insensitive
• [PAYARA-1060] - GlassFish HASSOFactory hardcoded replicated
• [PAYARA-1068] - Payara Micro's --outputUberJar should package any additional files/changes made to the --rootDir
• [PAYARA-1078] - Make JDBC connection validation use any configured statement timeout.
• [PAYARA-1087] - PhoneHome requires unique ID for Payara installations
• [PAYARA-1146] - Create a custom Hazelcast serialiser
• [PAYARA-1150] - When setting the File Rotation Limit to a value less than 500,000, the error message is not particularly informative
• [PAYARA-1184] - Payara Micro should output information about all deployed apps
• [PAYARA-1218] - Hazelcast help text in admin console is misleading
• [PAYARA-1234] - Deploying an application with an invalid name containing an accented char or space fails with unhelpful error message
• [PAYARA-1262] - Package notification artefacts in its own packager
• [PAYARA-1263] - HTTP(S) worker thread names now include their listener name
• [PAYARA-1276] - set relaxCacheVersionSemantics the default
• [PAYARA-1286] - Increase the autoBindRange default in Payara Micro
• [PAYARA-1324] - Simplify rolling upgrades
• [PAYARA-1330] - Send-Asadmin-Command does not print out or log the output of commands that do not inherently print anything out to the log
• [PAYARA-1343] - Support Hazelcast Partition Groups
• [PAYARA-1344] - Support Hazelcast Host Aware Partitioning in Payara Micro and Microprofile
• [PAYARA-1345] - Create more meaningful error message for JCache if Hazelcast is disabed
• [PAYARA-1346] - Hazelcast should be turned off when disabled dynamically
• [PAYARA-1347] - Notification listing asadmin commands need to display configuration for multiple notifiers
• [PAYARA-1407] - Enabling HealthCheck in Payara Micro without arguments fails uninformatively
• [PAYARA-1430] - Make Asadmin Recorder migrate better
• [PAYARA-1435] - Improvement on creating initial configuration for Healthcheck service
• [PAYARA-1437] - Remove unnecessary default values from the Healthcheck service commands
• [PAYARA-1438] - Remove unnecessary default values from the Request Tracing service commands
• [PAYARA-1447] - Ensure Hazelcast is booted before app deployments

Security Fixes

• [PAYARA-989] - Security Issue in Payara
• [PAYARA-1214] - Adapt to JDK fix for CVE-2016-3427
• [PAYARA-1216] - CVE-2016-3092 upgrade commons file upload
• [PAYARA-1217] - CVE-2016-0763 apply Security Permission for Global Context
• [PAYARA-1260] - Upgrade jline in nucleus pom for CVE-2013-2035

Upstream Bugs

• [PAYARA-1005] - Apps fail to deploy with empty beans.xml file
• [PAYARA-1007] - web.xml cannot override web-fragment.xml
• [PAYARA-1056] - Sums of thread pool statistics counters not correct
• [PAYARA-1105] - Using a custom log formatter leads to retaining only 10 history log files
• [PAYARA-1114] - Deadlock in a distributed transaction
• [PAYARA-1264] - JSP precompiling during deployment ignores settings in glassfish-web.xml

Component Upgrades

• [[PAYARA-1204] - Upgrade Weld version to 2.4.1.Final](https://github.com/payar...

Payara Blue 4.1.1.171

Bugs

• [PAYARA-737] - Resolve GLASSFISH-21532 GlobalTID breaks the equals/hashCode contract
• [PAYARA-934] - aliased password cannot be replaced by the value of the alias
• [PAYARA-995] - AS-WEB-CORE-00369 errors when using Hazelcast for session replication
• [PAYARA-1052] - MicroProfile UberJAR startup Grizzly error
• [PAYARA-1082] - Authorization stops working after app redeploy
• [PAYARA-1115] - Parameterised log messages are incorrectly escaped
• [PAYARA-1185] - JMS Service Binding Address not working correctly for application client
• [PAYARA-1188] - Negative Values for CountOpenConnections
• [PAYARA-1195] - Unable to deploy activemq-rar resource under Payara 4.1.1.164
• [PAYARA-1205] - Fix for PAYARA-1036 breaks Microprofile
• [PAYARA-1219] - Jersey EncodingFilter does not work in Payara 4.1.1.164
• [PAYARA-1223] - WELD-000163: Non-unique bean deployment identifier detected
• [PAYARA-1224] - Concurrency bug in SessionStatsProvider
• [PAYARA-1244] - Default role mapping setting broke the domain level setting
• [PAYARA-1254] - Spurious warning: "Severe: Unknow type constant pool 15 at position xxx"
• [PAYARA-1259] - Sending access logs to the console does not work as expected
• [PAYARA-1261] - Fix Warning: Context path from ServletContext: differs from path from bundle: /
• [PAYARA-1277] - Could not deploy simple war on cluster while Internet is off
• [PAYARA-1281] - Setting "Slow Query Log Threshold" to a positive value other than 1 causes password errors
• [PAYARA-1282] - JMX Monitoring service with dynamic=true will not be enabled unless the server is restarted
• [PAYARA-1283] - JMX monitoring service adding properties does not fail gracefully
• [PAYARA-1290] - JNDI conflict with local data sources
• [PAYARA-1380] - Fix session load NPE
• [PAYARA-1396] - Felix OSGi Web Console fails when installed

New Features

• [PAYARA-698] - Email Notifier
• [PAYARA-700] - JMS Notifier
• [PAYARA-701] - SNMP Notifier
• [PAYARA-702] - XMPP Notifier
• [PAYARA-703] - HipChat Notifier
• [PAYARA-704] - Slack Notifier
• [PAYARA-705] - Payara Micro (CDI Event Bus) Notifier
• [PAYARA-822] - Add simple API for registering a SAM
• [PAYARA-1039] – Public API JAR
• [PAYARA-1053] - Add a way to run asadmin commands against Payara Micro
• [PAYARA-1065] - Add controls for EJB pool size per EJB
• [PAYARA-1122] – Historical Request Traces
• [PAYARA-1125] – Historical Healthcheck entries
• [PAYARA-1138] - Extreme Classloader Isolation
• [PAYARA-1141] - Enable the DAS to send asadmin commands to Micro cluster members
• [PAYARA-1143] - Add support for CDI event bus into Payara Server
• [PAYARA-1383] - Admin Console integration for Health Check Service
• [PAYARA-1386] - Add support for substituting environment variables in domain.xml

Improvements

• [PAYARA-895] - Create new JAR format for microprofile
• [PAYARA-1044] - Payara Micro: Refresh logging configuration after set-log-levels
• [PAYARA-1048] - Payara Micro command line options should be case insensitive
• [PAYARA-1060] - GlassFish HASSOFactory hardcoded replicated
• [PAYARA-1068] - Payara Micro's --outputUberJar should package any additional files/changes made to the --rootDir
• [PAYARA-1078] - Make JDBC connection validation use any configured statement timeout.
• [PAYARA-1087] - PhoneHome requires unique ID for Payara installations
• [PAYARA-1146] - Create a custom Hazelcast serialiser
• [PAYARA-1150] - When setting the File Rotation Limit to a value less than 500,000, the error message is not particularly informative
• [PAYARA-1184] - Payara Micro should output information about all deployed apps
• [PAYARA-1218] - Hazelcast help text in admin console is misleading
• [PAYARA-1234] - Deploying an application with an invalid name containing an accented char or space fails with unhelpful error message
• [PAYARA-1262] - Package notification artefacts in its own packager
• [PAYARA-1263] - HTTP(S) worker thread names now include their listener name
• [PAYARA-1276] - set relaxCacheVersionSemantics the default
• [PAYARA-1286] - Increase the autoBindRange default in Payara Micro
• [PAYARA-1324] - Simplify rolling upgrades
• [PAYARA-1330] - Send-Asadmin-Command does not print out or log the output of commands that do not inherently print anything out to the log
• [PAYARA-1343] - Support Hazelcast Partition Groups
• [PAYARA-1344] - Support Hazelcast Host Aware Partitioning in Payara Micro and Microprofile
• [PAYARA-1345] - Create more meaningful error message for JCache if Hazelcast is disabed
• [PAYARA-1346] - Hazelcast should be turned off when disabled dynamically
• [PAYARA-1347] - Notification listing asadmin commands need to display configuration for multiple notifiers
• [PAYARA-1407] - Enabling HealthCheck in Payara Micro without arguments fails uninformatively
• [PAYARA-1430] - Make Asadmin Recorder migrate better
• [PAYARA-1435] - Improvement on creating initial configuration for Healthcheck service
• [PAYARA-1437] - Remove unnecessary default values from the Healthcheck service commands
• [PAYARA-1438] - Remove unnecessary default values from the Request Tracing service commands
• [PAYARA-1447] - Ensure Hazelcast is booted before app deployments

Security Fixes

• [PAYARA-989] - Security Issue in Payara
• [PAYARA-1214] - Adapt to JDK fix for CVE-2016-3427
• [PAYARA-1216] - CVE-2016-3092 upgrade commons file upload
• [PAYARA-1217] - CVE-2016-0763 apply Security Permission for Global Context
• [PAYARA-1260] - Upgrade jline in nucleus pom for CVE-2013-2035

Upstream Bugs

• [PAYARA-1005] - Apps fail to deploy with empty beans.xml file
• [PAYARA-1007] - web.xml cannot override web-fragment.xml
• [PAYARA-1056] - Sums of thread pool statistics counters not correct
• [PAYARA-1105] - Using a custom log formatter leads to retaining only 10 history log files
• [PAYARA-1114] - Deadlock in a distributed transaction
• [PAYARA-1264] - JSP precompiling during deployment ignores settings in glassfish-web.xml

Component Upgrades

• [[PAYARA-1204] - Upgrade Weld version to 2.4.1.Final](https://github.com/payar...

Payara Server 4.1.1.164

New Features

• 1063/PAYARA-182 - Java EE Concurrent Context Interceptor
• 1068/PAYARA-179 - Request Tracing for inbound JMS to MDB
• 1083/PAYARA-1038 - Add Request Tracing Event for JASPIC authentication
• 1097/PAYARA-178 - JDBC Context Interceptor
• 1099/PAYARA-756 - Request tracing events for start and stop of JTA transactions
• 1101/PAYARA-181 - JBatch Context interceptor
• 1107/PAYARA-931 - Integrate Request Tracing into Payara Micro
• 1131/PAYARA-999 - Enable jars within an application deployment to be excluded from CDI scanning
• 1142/PAYARA-867 - Option to disable the servlet container initializer
• 1152/PAYARA-618 - Enable the DAS to discover Payara Micro instances

Enhancements

• 980/PAYARA-846 - Add new improvements to payaradomain
• 996/PAYARA-936 - Provide default group to role mapping
• 1032/PAYARA-955 - Rolling upgrades for versioned apps
• 1034/PAYARA-824 - Disabling CDI in the deployment descriptor now overrides admin console setting
• 1053/PAYARA-733 - Add capability to output logs in JSON format
• 1076/PAYARA-1024 - Refactor Notification Service asadmin Commands for Simplicity
• 1076/PAYARA-1025 - Refactor Request Tracing asadmin Commands for simplicity
• 1082/PAYARA-1041 - Make notification service enabled by default for the log notifier
• 1102/PAYARA-1018 - Increase pool size of Managed Executor Service and Scheduled Executor Service
• 1111/PAYARA-1049 - Add a --deployDir option to do the same job as --deploymentDir in Payara Micro
• 1125/PAYARA-1107 - JCache beans created by JSR107Producer use generics
• 1126/PAYARA-1106 - Use name from CacheDefaults when injecting JCache
• 1130/PAYARA-923 - Provide option to compress log files on rotation
• 1150/PAYARA-1140 - Allow to use colon (:) to separate coordinates in maven deployer
• 1156/PAYARA-1071 - Admin console integration for JSON Log Formatter

Component Upgrades

• Jersey 2.22.2
• Hazelcast 3.7.1
• Eclipselink 2.6.3
• mail 1.5.6
• btrace 1.2.3
• Jackson 2.8.1
• Grizzly 2.3.28
• Weld 2.4.0.Final

Fixed Issues

• 668/PAYARA-947 - CDI EJB Field producers' validation fail with incompatible types
• 959/PAYARA-1010 - BufferUnderflowException in case of using java 8 with lambdas
• 986/PAYARA-1075 - Deployment of application fails when a resource adapter is not deployed to all instances
• 1000/PAYARA-690/PAYARA-813 - Cannot find the resource bundle error message when deploying / underlying EAR applications
• 1041/PAYARA-1012 - Payara Embedded stopped working in .163 due to request tracing
• 1044/PAYARA-1129 - Perform preInvoke and postInvoke steps symmetrically in EJB BaseContainer
• 1046/PAYARA-1034 - NPE when accessing Notification Service in the admin console on a 162 domain with 163 binaries
• 1049/PAYARA-994/PAYARA-1023 - Healthcheck service can't add a new checker dynamically / NullPointerException when dynamically registering healthcheck services for the first time
• 1064/PAYARA-935 - Fix "Illegal non-string type" for request tracing, notification, healthcheck, and asadmin recorder services
• 1067/PAYARA-1035 - Request Tracing is not dynamic in domain migrated from 162 to 163
• 1075/PAYARA-993 - Update Grizzly to 2.3.26 to fix PAYARA-797
• 1076/PAYARA-1040 - Payara Micro does not force redeploy when domain.xml or rootDir is used
• 1079/PAYARA-956 - ManagedExecutorService MBean attempts to register multiple times
• 1081/PAYARA-917 - Jaspic - forward from SAM injected request tests fail
• 1084/PAYARA-988 - Asadmin command to configure hogging threads checker is missing
• 1110/PAYARA-1076 - PAYARA-1076 make LazyBootPersistence manager more null safe on misconfiguration
• 1116/PAYARA-1083 - disable and deploy commands should wait for all applications to deploy
• 1128/PAYARA-1104 - Wrong redirect of WebService endpoint to https
• 1129/PAYARA-1081 - ClassNotFoundException for JaxbAnnotationIntrospector upon first request to REST endpoint
• 1132/PAYARA-954 - Update Service descriptions to replace "GlassFish" with "Payara"
• 1136/PAYARA-1036 - @ViewScoped, @FlowScoped, @ConversationScoped not working on Payara Micro
• 1139/PAYARA-1126 - Cache Interceptors should cast to Throwable not Exception when Caching
• 1140/PAYARA-934 - aliased password cannot be replaced by the value of the alias
• 1144/PAYARA-1113 - Request Tracing does not process thresholds of less than one millisecond
• 1145/PAYARA-1130 - Comparing elapsed time to threshold should be done in nanoseconds
• 1149/PAYARA-1134 - When Payara Micro deploys a war called ROOT.war its context root is /ROOT when it should be /
• 1159/PAYARA-1127 - Unable to set ClientInfo for connection with H2 1.4.192

Security Fixes

• 1024/PAYARA-989 - Security Issue in Payara
• 1051/PAYARA-1011 - Fix CVE-2016-5388

Upstream Fixes

• 1052/PAYARA-1010/GLASSFISH-21510 - BufferUnderflowException in case of using java 8 with lambdas
• 1089/PAYARA-1067 - Undefined behaviour when interceptor method is overloaded in interceptor class
• 1090/PAYARA-892/GLASSFISH-20606 - create-domain assigns wrong values for JMS port
• 1123/PAYARA-1056 - Sums of thread pool statistics counters not correct
• 1157/PAYARA-1008 - Fix PWC6117: File "null" not found errors

Payara Blue 4.1.1.164

New Features

• 1063/PAYARA-182 - Java EE Concurrent Context Interceptor
• 1068/PAYARA-179 - Request Tracing for inbound JMS to MDB
• 1083/PAYARA-1038 - Add Request Tracing Event for JASPIC authentication
• 1097/PAYARA-178 - JDBC Context Interceptor
• 1099/PAYARA-756 - Request tracing events for start and stop of JTA transactions
• 1101/PAYARA-181 - JBatch Context interceptor
• 1107/PAYARA-931 - Integrate Request Tracing into Payara Micro
• 1131/PAYARA-999 - Enable jars within an application deployment to be excluded from CDI scanning
• 1142/PAYARA-867 - Option to disable the servlet container initializer
• 1152/PAYARA-618 - Enable the DAS to discover Payara Micro instances

Enhancements

• 980/PAYARA-846 - Add new improvements to payaradomain
• 996/PAYARA-936 - Provide default group to role mapping
• 1032/PAYARA-955 - Rolling upgrades for versioned apps
• 1034/PAYARA-824 - Disabling CDI in the deployment descriptor now overrides admin console setting
• 1053/PAYARA-733 - Add capability to output logs in JSON format
• 1076/PAYARA-1024 - Refactor Notification Service asadmin Commands for Simplicity
• 1076/PAYARA-1025 - Refactor Request Tracing asadmin Commands for simplicity
• 1082/PAYARA-1041 - Make notification service enabled by default for the log notifier
• 1102/PAYARA-1018 - Increase pool size of Managed Executor Service and Scheduled Executor Service
• 1111/PAYARA-1049 - Add a --deployDir option to do the same job as --deploymentDir in Payara Micro
• 1125/PAYARA-1107 - JCache beans created by JSR107Producer use generics
• 1126/PAYARA-1106 - Use name from CacheDefaults when injecting JCache
• 1130/PAYARA-923 - Provide option to compress log files on rotation
• 1150/PAYARA-1140 - Allow to use colon (:) to separate coordinates in maven deployer
• 1156/PAYARA-1071 - Admin console integration for JSON Log Formatter

Component Upgrades

• Jersey 2.22.2
• Hazelcast 3.7.1
• Eclipselink 2.6.3
• mail 1.5.6
• btrace 1.2.3
• Jackson 2.8.1
• Grizzly 2.3.28
• Weld 2.4.0.Final

Fixed Issues

• 668/PAYARA-947 - CDI EJB Field producers' validation fail with incompatible types
• 959/PAYARA-1010 - BufferUnderflowException in case of using java 8 with lambdas
• 986/PAYARA-1075 - Deployment of application fails when a resource adapter is not deployed to all instances
• 1000/PAYARA-690/PAYARA-813 - Cannot find the resource bundle error message when deploying / underlying EAR applications
• 1041/PAYARA-1012 - Payara Embedded stopped working in .163 due to request tracing
• 1044/PAYARA-1129 - Perform preInvoke and postInvoke steps symmetrically in EJB BaseContainer
• 1046/PAYARA-1034 - NPE when accessing Notification Service in the admin console on a 162 domain with 163 binaries
• 1049/PAYARA-994/PAYARA-1023 - Healthcheck service can't add a new checker dynamically / NullPointerException when dynamically registering healthcheck services for the first time
• 1064/PAYARA-935 - Fix "Illegal non-string type" for request tracing, notification, healthcheck, and asadmin recorder services
• 1067/PAYARA-1035 - Request Tracing is not dynamic in domain migrated from 162 to 163
• 1075/PAYARA-993 - Update Grizzly to 2.3.26 to fix PAYARA-797
• 1076/PAYARA-1040 - Payara Micro does not force redeploy when domain.xml or rootDir is used
• 1079/PAYARA-956 - ManagedExecutorService MBean attempts to register multiple times
• 1081/PAYARA-917 - Jaspic - forward from SAM injected request tests fail
• 1084/PAYARA-988 - Asadmin command to configure hogging threads checker is missing
• 1110/PAYARA-1076 - PAYARA-1076 make LazyBootPersistence manager more null safe on misconfiguration
• 1116/PAYARA-1083 - disable and deploy commands should wait for all applications to deploy
• 1128/PAYARA-1104 - Wrong redirect of WebService endpoint to https
• 1129/PAYARA-1081 - ClassNotFoundException for JaxbAnnotationIntrospector upon first request to REST endpoint
• 1132/PAYARA-954 - Update Service descriptions to replace "GlassFish" with "Payara"
• 1136/PAYARA-1036 - @ViewScoped, @FlowScoped, @ConversationScoped not working on Payara Micro
• 1139/PAYARA-1126 - Cache Interceptors should cast to Throwable not Exception when Caching
• 1140/PAYARA-934 - aliased password cannot be replaced by the value of the alias
• 1144/PAYARA-1113 - Request Tracing does not process thresholds of less than one millisecond
• 1145/PAYARA-1130 - Comparing elapsed time to threshold should be done in nanoseconds
• 1149/PAYARA-1134 - When Payara Micro deploys a war called ROOT.war its context root is /ROOT when it should be /
• 1159/PAYARA-1127 - Unable to set ClientInfo for connection with H2 1.4.192

Security Fixes

• 1024/PAYARA-989 - Security Issue in Payara
• 1051/PAYARA-1011 - Fix CVE-2016-5388

Upstream Fixes

• 1052/PAYARA-1010/GLASSFISH-21510 - BufferUnderflowException in case of using java 8 with lambdas
• 1089/PAYARA-1067 - Undefined behaviour when interceptor method is overloaded in interceptor class
• 1090/PAYARA-892/GLASSFISH-20606 - create-domain assigns wrong values for JMS port
• 1123/PAYARA-1056 - Sums of thread pool statistics counters not correct
• 1157/PAYARA-1008 - Fix PWC6117: File "null" not found errors

Payara Server 4.1.1.163

Release Highlights

The 163 release of Payara will feature a couple of new tech previews. These are new features added to Payara which we do not recommend are used on production systems.
Request Tracing is a new service that will allow Payara to track and log information about the requests it handles.
Payara now offers a JMX Monitoring Service. Once configured, Payara Server will monitor and log the values of attributes that have been listed for monitoring.

Updated Modules

• ibm.jbatch.container.version 1.0.1.payara-p2
• Hazelcast 3.6.4
• Grizzly 2.3.25
• mimepull 1.9.6
• javax.batch-api.version 1.0.1
• jbatch.container.version 1.0.1
• jbatch.spi.version 1.0.1
• Weld 2.3.5.Final
• Tyrus 1.13

New Features

This section details the newly developed additions to Payara Server.

• PAYARA-168 - Integrate HealthCheck notifications with the Notification Service
• PAYARA-612 - Create a general notification service
• 856/PAYARA-186 - Hazelcast Based EJB Persistent Timer Store for Payara Micro
• 857/PAYARA-592 - Monitoring for Concurrent Resources
• 939/PAYARA_174 - Initial Tech Preview implementation of Request Tracing
• 975/PAYARA-811 - Monitor agent to write JMX metrics to file periodically
• 977/PAYARA-180 - CDI Interceptor api that can be used to wrap any CDI call to be traced by Request Tracing

Enhancements

This section details the issues marked as enhancements that have been implemented for this release.

• PAYARA-177 - Trace EJB Method Calls
• PAYARA-183 - asadmin commands to configure and control request tracing
• PAYARA-697 - Create Notification Service Log Notifier
• PAYARA-757 - Request tracing of outbound WebService calls
• PAYARA-758 - Request tracing of outbound REST calls
• 754/PAYARA-755 - Request tracing support for WebSockets
• 787/PAYARA-729 - Send Payara access logs to stdout/stderr
• 820/PAYARA-740 - Add a --version option to Payara Micro
• 836/PAYARA-746 - Add validation to prevent you entering a negative value for fish.payara.jts.RecoveryResynchTimeout property
• 851/PAYARA-754 - Add extra output location validation for the Asadmin Recorder service
• 855/PAYARA-827 - JTA Transaction Timer Thread should be named
• 859/PAYARA-791 - server.log file empty for Payara micro
• 862/PAYARA-823 - DataSource is silently defaulted to jdbc/__default on any lookup failure
• 865/PAYARA-683 - When EAR is deployed, it is not possible to see details of EJB modules in admin console
• 891/PAYARA-184 - Admin Console Integration for configuration of request tracing
• 894/PAYARA-848 - Admin Console Integration for configuration of Notification Service
• 897/PAYARA-169 - Admin Console integration to display Notifications on server tab
• 903/PAYARA-628 - Move Hazelcast and JBatch configuration into the tree view rather than its current location on the tab view. Only members should be on the tab view.
• 905/PAYARA-796 - Add license key field for Payara Scales
• 913/PAYARA-845 - Add option to disable the Server Header
• 915/PAYARA-832 - Create new version identifier for Payara Blue
• 916/PAYARA-847 - Change the thread-pool for the Admin HTTP listener in a cluster environment
• 924/PAYARA-859 - Request for finer-grained slow sql logger with miliseconds
• 934/PAYARA-839 - Disabled apps have no contextRoot param after restart
• 943/PAYARA-909 - healthcheck commands do not accept configurations as a target
• 947/PAYARA-927 - Merge two Request Tracing Service configuration page into one
• 950/PAYARA-928 - Merge two Notification Service configuration page into one
• 957/PAYARA-926 - Request Tracing for EJB Timers
• 968/PAYARA-851 - Access logging command line option for Payara Micro
• 970/PAYARA-731 - Shrink the Payara Micro Jar
• 974/PAYARA-836 - Allow user to use their own logging.properties file for Payara Micro
• 975/PAYARA-771 - Create asadmin commands for the monitoring logger
• 943/PAYARA-909 - healthcheck commands do not accept configurations as a target

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.

• 244/PAYARA-470 - JTS recovery hangs for the full length of the recovery timeout and then succeeds
• PAYARA-580 -Investigate Closed Entity Factory possible bug
• PAYARA-682 - Properties substitustion does not work when EJB module with application-scoped datasource is deployed
• 794/PAYARA-776 - Windows service is named "domain1 GlassFish Server"
• 798/PAYARA-775 - Unwrapping principal interferes with JASPIC's register session
• 799/PAYARA-710 - Fix CVE-2012-2098
• 807/PAYARA-643 - The JMS Availability tab contains a deep link to Oracle docs
• 808/PAYARA-594 - Spurious AllPermission warning
• 812/PAYARA-382 - Fix GitHub issue 384 spurious SEVERE log message when deploying WebService
• 816/PAYARA-742 - Eclipselink generates broken SQL for Informix
• 822/PAYARA-355 - thousands of ClassNotFound warnings while deploying an EAR with many WAR's
• 825/PAYARA-800 - Payara Micro Maven Deployer gives a FileNotFoundException
• 828/PAYARA-794 - NPE in LazyBootPersistenceManager if configured JNDI name does not point to a valid datasource
• 829/PAYARA-803 - No LoginModules configured for jdcbRealm on Payara Micro
• 831/PAYARA-802 - Payara Domain is missing -Djavax.xml.accessExternalSchema=all
• 834/PAYARA-799 - The exception: "java.lang.IllegalArgumentException: PWC2788: setAttribute: Non-serializable attribute" will occur when a web-fragment.xml with is found
• 835/PAYARA-724 - The admin console does not render escape characters on the log levels page
• 837/PAYARA-639 - Weld NPE when invalidating sessions
• 845/PAYARA-664 - NullPointerException during WebDirContext.lookupFromJars probably caused by race conditions
• 847/PAYARA-734 - Admin console should spit out a warning if JMS destination name contains a forward slash
• 852/PAYARA-795 - Payara Blue on IBM JDK invalid JVM options
• 854/PAYARA-826 - ClassNotFoundException with JSR107 annotations on stateless session bean
• 867/PAYARA-821 - JoinFetch annotation in EclipseLink ignores default
• 889/PAYARA-808 - j-interop-repackaged.jar is missing in Payara Server 162
• 893/PAYARA-853 - thread pool statistics counters not correct
• 899/PAYARA-852 - New admin console design doesn't display on Chinese, Japanese and korean
• 908/PAYARA-863 - Payara no longer starts in windows
• 920/PAYARA-900 - NPE in Payara Micro when --noCluster
• 922/PAYARA-889 - Hazelcast not booting when started from the Configurations.
• [925/PAYARA-90...

Payara Server 4.1.1.162

Release Highlights

Our highlights for the 162 release are our new asadmin command recorder, Payara Server's new ability to create uber jars and a new EAR scoped class loader.

The asadmin recorder feature will allow you view the commands you have run from the admin console. These can be used to investigate what the console is really doing or used in automation scripts.

Payara Micro now has --outputUberJar option that allows you to create easily distributed uber-jars from your war files.

EAR Scoped classloader that loads classes from within the EAR providing the ability to override server classes.

Payara Server and Payara Micro can now cluster together enabling new cluster topologies for cloud based and/or containerised deployments!

New Features

This section details the newly developed additions to Payara Server.

• 636/PAYARA-603 - Payara Micro Enhancements
• 669/PAYARA-626 - added support for Hazelcast Lite Members
• 687/PAYARA-249 - Payara Micro Maven Deployer
• 697/PAYARA-163 - connection pool checker impl
• 724/PAYARA-201 - Initial working Asadmin Recorder with Admin Console integration
• 777/PAYARA-629 - Disable CDI for an entire deployment in deployment descriptor
• 627 - Invocation Webservice deployed from directory
• 784/PAYARA-685 - Phone Home Service Creation

Updated Modules

This section details the modules that have been updated since the last release (4.1.1.161.1).

• Guava 18.0
• Weld 2.3.2.Final
• Tyrus 1.12
• hk2 2.4.0
• Mojarra 2.2.13
• Grizzly 2.3.24
• Hazelcast 3.6.2

Enhancements

This section details the issues marked as enhancements that have been implemented for this release.

• 602/PAYARA-639 - Unique IDs are kept based on the name of the EJB
• 677/PAYARA-593 - Cleanup on Admin Console
• 691/PAYARA-610 - integrated healthcheck with payara micro
• 694/PAYARA-263 - Autobinding port precedence warnings
• 711/PAYARA-576 - Integrate upstream pull request for the 4.1.162 release
• 712/PAYARA-675 - Payara Micro can deploy exploded archive
• 718/PAYARA-745 - Fix isSupportClientInfo in ConnectionHolder40 for old drivers
• 720/PAYARA-676 - Restart cluster asadmin command
• 728/PAYARA-679 - Uber Jar command line option
• 733/PAYARA-743 - Prevent duplicate server respawn when run under supervision
• 738/PAYARA-692 - Remove dependency on Hazelcast
• 739/PAYARA-687 - Implement Hazelcast Cluster Group
• 745/PAYARA-720 - plugin versions upgraded for to be compatible with maven upgrade
• 750/PAYARA-688 - Add ability to pass a system properties file to Payara Micro
• 776/PAYARA-707 - edit of message for tls
• 749/PAYARA-686 - Clean up the help message by indicating whether a command line flag has a parameter or not
• 772/PAYARA-728 - Implement new index page
• 774/PAYARA-672 - add PostgreSQL ejbtimer table creation sql
• 785/PAYARA-390 - allow monitoring of asynchronous methods
• 786/PAYARA-677 - Add support for overriding app server libraries using ScopedEARClassloader on domain level

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.

• 617/PAYARA-657 - GLASSFISH-21486: EntityManager should not be detached in extended Persistence context
• 637/PAYARA-599 - Remove Boot time OSGI warnings
• 640/PAYARA-658 - GLASSFISH-20818: Pass passwords from passwordfile to commands
• 649/PAYARA-624 - mixed cluster session replication
• 656/PAYARA-594 - Spurious AllPermission warning
• 658/PAYARA-542 - Cannot enable secure ciphers for admin listener
• 659/PAYARA-588 - Excessive logging from the ASURL classloader
• 667 - #505 is not fixed when TxType is REQUIRES_NEW
• 672/PAYARA-631 - rollbacked pax-logging and patched the webservices-osgi again
• 673 - Problems on deployment of OSGi hybrid bundles
• 678/PAYARA-663 - Cannot find resource bundle com.sun.logging.enterprise.resource.corba
• 681/PAYARA-659 - Fix failing transaction recovery when OSGi applications are present
• 682/PAYARA-671 Always perform clean up on application on DAS upon undeployment
• 683/PAYARA-660 - Resolve com.sun.aas.instanceName in JVM arguments
• 686/PAYARA-578 - Payara Blue should use Metro AIX bundle
• 695/PAYARA-637 - Only-1-Health-Check-Service-is-run-if-no-name-is-specified
• 698/PAYARA-661 - empty value for sql-trace-listeners in a connection-pool fails validation
• 699/PAYARA-665/PAYARA-535 - force JarFileFactory to close all cached Jar Files/Undeploy App leaves stale NFS handle behind
• 702/PAYARA-670 - Payara not showing modules for versioned application
• 704/PAYARA-541/PAYARA-663 - Fix resource bundle issues
• 709/PAYARA-606 explicitly set TCCL before attempting Batch repository purge on undeployment
• 716/PAYARA-744 - Fixed logging dependencies of several modules
• 717 - isSupportClientInfo in ConnectionHolder40 is not implemented correctly
• 726/PAYARA-681 - changed gosh command in XML files
• 727/PAYARA-684 - enabled initializing FacesInitializer while using useBundledJsf param
• 729/PAYARA-693 - Payara micro: setting SSL trustStore / keyStore manually
• 734/PAYARA-696 - added default name to connection pool checker
• 735/PAYARA-494 - Help button displays wrong page and pop-up page is fixed
• 740/PAYARA-652 - ensure rootDir option does not override domainCofig option
• 743/PAYARA-636 - setting values for the checker services dynamically is now working correctly
• 752/PAYARA-662 - Set TLSv1.2 as default for the asadmin client
• 757/PAYARA-601 - changed warning note in asenv.conf/asenv.bat
• 761/PAYARA-727 - Fixed GLASSFISH-21536 possible NPE in SQLTraceRecord
• 763/PAYARA-674 - The "Restart Required" screen does not have the warning about restarting when Payara is a service
• 762/PAYARA-717 - invokeMethod now depends on getDeclaredMethod as recursive instead of getMethod
• 766/PAYARA-708 - Admin-console-still-shows-Grizzly-Snoop-option-despite-the-feature-being-removed
• 783/PAYARA-738 - references to weld osgi bundle.jar should be fixed

Known Issues

Known issues can be seen on our GitHub issues page here: https://github.com/payara/Payara/issues

Payara Blue 4.1.1.162

Merge pull request #788 from Pandrex247/PAYARA-753

PAYARA-753

Payara Server 4.1.1.161.1

Due to a number of issues brought on by our inclusion of Pax Logging in Payara Server 4.1.1.161, we're releasing a patched version of Payara Server that should alleviate these issues by removing Pax Logging.

Updated Modules

This section details the modules that have been updated since the last release (4.1.1.154).

• Metro 2.3.2-b608.payara-p3 (Removed Pax-Logging)

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.

• 637/PAYARA-599 – Cannot start bundle ../core.jar because it is not contained in the list of installed bundles
• 649/PAYARA-624 – Mixed Payara Micro and Payara Server cluster causes session loss
• 656/PAYARA-594 – Spurious AllPermission warning
• 658/PAYARA-542 – Cannot enable secure ciphers for admin-listener
• 659/PAYARA-588 – Excessive logging from the ASURL Classloader
• 667/PAYARA-640 – Payara does not rollback when TxType is REQUIRES_NEW
• 672/PAYARA-631 – Problems with Pax-Logging
• 673/PAYARA-642 – Fix Classloader issue when bootstrapping the ORB for OSGi bundle deployments

Known Issues

Known issues can be seen on our GitHub issues page here: https://github.com/payara/Payara/issues

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