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.

The following error is thrown when starting Kaazing Gateway using Java 9:

java.lang.NoClassDefFoundError: javax/annotation/Resource

Workaround: Use Java 8

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)