Release Notes: Kaazing Gateway

5.7.3

Release Date: October 10, 2017

What's New

  • Bug fixes

Known Issues

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • Deprecated update.check as a service to simplify the configuration. To disable the update check, set the system flag org.kaazing.gateway.server.UPDATE_CHECK=false when starting the Gateway (tickets#1121)

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.7.2

Release Date: September 1, 2017

What's New

  • Bug fixes

Known Issues

  • The connection limit in the license is ignored, and the default 50 connection limit is enforced.

    Use version 5.7.3 or higher in order to utilize all connections specified in the license.

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • Deprecated update.check as a service to simplify the configuration. To disable the update check, set the system flag org.kaazing.gateway.server.UPDATE_CHECK=false when starting the Gateway (tickets#1121)

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.7.1

Release Date: July 28, 2017

What's New

  • Fixed an issue when running in a JVM configured with a HTTP proxy. Gateway now resolves the proxy hostname on each invocation, and sends the fully qualified target hostname instead of the resolved IP address in the HTTP CONNECT (tickets#1132)

Known Issues

  • The connection limit in the license is ignored, and the default 50 connection limit is enforced.

    Use version 5.7.3 or higher in order to utilize all connections specified in the license.

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • Deprecated update.check as a service to simplify the configuration. To disable the update check, set the system flag org.kaazing.gateway.server.UPDATE_CHECK=false when starting the Gateway (tickets#1121)

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.7.0

Release Date: July 19, 2017

What's New

Known Issues

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • Deprecated update.check as a service to simplify the configuration. To disable the update check, set the system flag org.kaazing.gateway.server.UPDATE_CHECK=false when starting the Gateway (tickets#1121)

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.6.2

Release Date: May 18, 2017

What's New

  • Fixed a security issue (tickets#1092)

Known Issues

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.6.1

Release Date: April 27, 2017

What's New

  • Early access: Added http.redirect service (roadmap#1027)

    This service lets you redirect requests to a different URL. For example, a user user accidentially enters a http:// URL when your service accepts connections on a https:// URL. See documentation

    To enable this early access feature, use the early access flag and set http.redirect.

  • Fixed a known issue: Reduce cluster recovery time when a cluster member leaves the cluster (tickets#976)

Known Issues

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.6.0

Release Date: March 22, 2017

What's New

  • Use native HTTP 302 redirects for load balancing (roadmap#1070)

    This means any standards-based WebSocket client can participate when using Kaazing Gateway for load balancing and high availability.

  • Added support for mesh high availability in Enteprise Shield configurations (roadmap#1069)

    This lets you have an independent number of gateways in either tier for Enterprise Shield. See the Docker-based tutorial for an example.

  • Fixed security issue for CVE-2017-6910. (tickets#1019)

Known Issues

  • Cluster members may take up to a minute to notice when another cluster member leaves the cluster (tickets#976)

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.5.0

Release Date: February 28, 2017

What's New

  • Added support for mobile notifications (roadmap#674)

    This feature enables you to notify users that messages are awaiting them when their Kaazing mobile app is in the background on their device. See documentation

Known Issues

  • Cluster members may take up to a minute to notice when another cluster member leaves the cluster (tickets#976)

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.4.1

Release Date: February 13, 2017

What's New

  • Write warning to log when a HTTP 1.0 request is first received with http.proxy service (roadmap#1024)

Known Issues

  • Cluster members may take up to a minute to notice when another cluster member leaves the cluster (tickets#976)

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.4.0

Release Date: January 15, 2017

What's New

  • Added HTTP proxy service (roadmap#15)

    Keep all inbound firewall ports by forwarding all HTTP and WebSocket traffic with HTTP proxy in an Enterprise Shield configuration. See documentation

  • Updated Hazelcast to 3.7.4 (roadmap#811)

  • Updated bundled ActiveMQ to version 5.14.1. (roadmap#984)

  • Minor tweaks to gateway-config.xml and log4j-config.xml (gateway/709)

  • Fixed bug where where a SOCKS reverse connect on a WSN transport was case sensitive. (tickets#788)

  • Fixed by where killing sessions by Principal in JMX sporadically failed if attempted too quickly during session initialization (tickets#448)

  • Fixed issue where JMX session close notification was not sent when killing session by principal (tickets#412)

Known Issues

  • Cluster members may take up to a minute to notice when another cluster member leaves the cluster (tickets#976)

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.3.0

Release Date: November 15, 2016

What's New

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • maximum.pending.sends no longer has any effect in the jms.proxy service. It is still supported in the jms service (roadmap#1001)

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.2.1

Release Date: November 3, 2016

What's New

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.1.5

Release Date: October 18, 2016

What's New

  • Bug fixes

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.1.4

Release Date: October 3, 2016

What's New

  • Fixed: In some circumstances gateway used 25% CPU while idle (tickets#769)

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.1.3

Release Date: September 20, 2016

What's New

  • Early access: Added TURN proxy service. Use the early access flag and set turn.proxy (roadmap#878)

  • Fixed: Shared wildcard topic subscriptions not working with ibmmq service (enterprise.gateway/422)

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.1.2

Release Date: September 9, 2016

What's New

  • Added <symbolic-link> property to directory service (roadmap#867) Learn more

  • Added update.check service to check if a newer version is available (roadmap#735) Learn more

  • Early access: Added IBM MQ service. Use the early access flag and set ibmmq (roadmap#902)

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.1.1

Release Date: August 21, 2016

What's New

  • Early access: Send mobile notification messages to iOS and Android devices. Use the early access flag and set notifications (roadmap#834)

  • Fixed: Gateway not specification compliant for invalid headers (gateway/637)

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.1.0

Release Date: August 8, 2016

What's New

  • HTTP connector can follow 302 redirects via <connect-option> property. (tickets#290)

    Example:

    <http.maximum.redirects>2<http.maximum.redirects>

  • Change default behavior of gateway to always require login module to pass when there is a login module present in the security realm (roadmap#825)

  • Early access: Balancer service can balance using HTTP redirect or WSX-wrapped HTTP redirect. Use the early access flag and set wsn.302.redirect or wsx.302.redirect (tickets#290)

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.0.3

Release Date: July 20, 2016

What's New

  • Early access: Support for Redis messaging. Use the early access flag and set redis. (roadmap#9)

  • Early access: Support for property-based routing and virtual queues. Use the early access flag and set vq. (roadmap#721) Learn more

Fixes

  • Directory Service responds with 200 OK when If-Modified-Since matches Last-Modified from previous response (tickets#383)

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.0.2

Release Date: August 8, 2016

What's New

  • Added early access flag to allow access to beta features (tickets#826) Learn more

Fixes

  • Fixed an issue in socks transport where one service was able to bind to another service (tickets#567)

  • Fixed spurious warnings about SLF4J in log file (gateway/80)

  • Fixed issue where gateway failed to start if deprecated session service is in the configuration (tickets#576)

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development

5.0.1

Release Date: May 1, 2016

What's New

  • Docker deployment (roadmap#146) Learn more

  • IP whitelist to allow connections only from trusted endpoints (roadmap#427) Learn more

  • Added the ability to specify a NIC (Network Interface Card) name rather than a hostname or IP address for inbound requests in the configuration. (roadmap#488) Learn more

    This feature makes your configuration portable to other instances with fewer (or no) changes, for example when setting up a cluster.

  • Added a JMX attribute to session objects which show the roundtrip latency from the gateway to the client (roadmap#488)

    Enable this by setting <ws.inactivity.timeout> in the <accept-options> of your service.

  • Added a JMX operation on a service to kill all sessions by a specified Principal (roadmap#508)

    If you have a Principal that stores the userid, for example, then you can kill all sessions for a specific userid in a single operation.

  • Added a JMX attribute to the service object that shows the total session count for the service (roadmap#506)

  • Always show when clients disconnect in the log, and provide a reason, if known (roadmap#551)

Known Issues

  • Killing sessions by Principal in JMX can sporadically fail if attempted too quickly during session initialization (tickets#448)

    Workaround: Allow the session to fully initialize before terminating it using JMX.

  • JMX session close notification not sent when killing session by principal (tickets#412)

    Workaround: No workaround

  • Using <tcp.bind> or <http.bind> in a service whose <accept>-s match the SOCKS host and port will cause a bind conflict (tickets#377)

    Workaround: Use <*.transport> instead. See documentation

  • APNs support not included in this release (roadmap#476)

    Workaround: No workaround

  • Gateway fails to start if deprecated session service is in the configuration (tickets#576)

    Workaround: The session service has been desupported for a long time. Remove it from the configuration and restart the gateway

  • Using WS over SOCKS gives errors (tickets#1119)

    Workaround: Consider using the recommended configuration with the <http.proxy> service, or use pipe over SOCKS instead.

  • Due to a known issue with Kaspersky antivirus software, WebSocket connections may fail if Kaspersky is enabled (tickets#602)

    Workaround: Use TLS or disable the antivirus software.

Deprecations

  • In the JMX API, services are now registered by name and not the first <accept> URL (tickets#411)

  • Removed <properties><accept> from broadcast service (roadmap#477)

  • The com.kaazing.gateway.amqp.server.spi.AmqpPrincipal class has been renamed to com.kaazing.gateway.service.amqp.spi.AmqpPrincipal (tickets#171)

  • Removed Command Center and SNMP service (tickets#519)

System Requirements

  • Java Developer Kit (JDK) or Java Runtime Environment (JRE) Java 8 (version 1.8.0_77) or higher

  • While Kaazing supports a variety of platorms, the following operating systems are recommended for production use:

    • RHEL / CentOS 5 or higher
    • Debian 7 or higher
    • Ubuntu LTS 12.04, LTS 14.04, LTS 16.04
    • Windows Server 2008 R2, 2012

    In addition, other platforms like Windows Desktop and Mac OSX are suitable for development