Download Kaazing WebSocket Gateway 4.0.9 JMS Edition Hotfix 17 here.

This hotfix is cumulative for all the previous hotfixes from the same patch
release.

List of fixed issues

  4.0.9.x-hotfix17

  Issue: kaazing/tickets#528
    Kaazing client libs for iOS will now target iOS version 8.4.

  4.0.9.x-hotfix16

  Issue: kaazing/tickets#410
    Fixed an issue when Gateway reconnects the Javascript client will
    disconnect with a duplicate subscription id error.

  4.0.9.x-hotfix15

  Issue: kaazing/tickets#378
    Fixed memory leaks in Kaazing WebSocket iOS Client framework
    and Kaazing JMS iOS Client framework. These frameworks now
    support iOS 9.2. Since App Transport Security from Apple
    is turned on by default in iOS 9, the app needs to be configured
    so that it can continue to make HTTP requests to access the
    Gateway for revalidation as well as emulation purposes.
    (See configuration instructions for more details)

  4.0.9.x-hotfix14

  Issue: kaazing/tickets#390
    Fixed an issue in the jms authorization module where credential
    checks on revalidate were using the original token.

  Issue: kaazing/tickets#346
    Fixed an issue where a URL was used in the source code which
    causes some security scans to fail.

  4.0.9.x-hotfix13

  Issue: kaazing/tickets#329
    Fixed an issue where Gateway throws an exception: Unexpected frame type
    on Firefox Developer Edition.

  4.0.9.x-hotfix12

  Issue: kaazing/tickets#289
    Provided a featrue to enable encrypt env.java.naming.security.credentials
    in the configuration file.
    (See configuration instructions for more details)

  Issue: kaazing/tickets#266
    Fixed an issue where balancer service was not always rediscovering
    cluster members balance URIs on restart.

  4.0.9.x-hotfix09

  Issue: kaazing/tickets#272
    Fixed an issue to turn off falling back to long polling in
    .Net client via websocket factory property.
    (See configuration instructions for more details)

  Issue: kaazing/tickets#251 
    Fixed an issue where TCP/SSL connections stay open indefinitely
    via system property. (See configuration instructions for more details)

  4.0.9.x-hotfix07

  Issue: kaazing/tickets#227
    Fixed an issue for initial connection failure where
    buffer fills very slowly with new data to read for .NET/Xamarin.

  Issue: kaazing/tickets#241
    Fixed an issue for .NET/Xamarin client closes upstream connection
    forcing full TLS handshake to occur on the next upstream.

  Issue: kaazing/tickets#224
    Fixed an issue of gateway connection leak with WSE client.

  4.0.9.x-hotfix06

  Issue: kaazing/tickets#118
    Fixed an issue in cluster balancer service which prevented
    servers to properly bind and unbind from the service.

  4.0.9.x-hotfix05

  Issue: kaazing/tickets#151
    Fixed an out of memory issue on gateway server.

  4.0.9.x-hotfix04

  Issue: kaazing/tickets#109
    Fix StompMessageEncoder to avoid mutating the message.

  Issue: kaazing/tickets#116
    Log contains exception stack messages "Early termination
    of IO session" and "Network connectivity has been lost".

  4.0.9.x-hotfix03

  Issue: kaazing/tickets#144
    Added a flag in the WebSocket JavaScript client named
    KAAZING_INTERNAL_DISABLE_BLOB in order to disable Kaazing's
    Blob implementation when necessary.

  4.0.9.x-hotfix02

  Issue: kaazing/tickets#103
    Fixed an issue where durable subscriber clients fail to get
    messages after varying lengths of time.

  4.0.9.x-hotfix01

  Issue: kaazing/tickets#81
    Fixed an issue where the authenticated subject was not made
    available to JmsUserIdentityResolver if authentication is done
    via the stomp.jms authentication.realm service property.

See README for more information.