Download Kaazing WebSocket Gateway 4.0.9 JMS Edition Hotfix 08 here.
Closed Issues in 4.0.9.x-hotfix08
Defect ID: kaazing/tickets#224
Fixed an issue of gateway connection leak with WSE client
Defect ID: kaazing/tickets#241
Fixed an issue for .NET/Xamarin client closes upstream connection
forcing full TLS handshake to occur on the next upstream
Defect ID: kaazing/tickets#227
Fixed an issue for initial connection failure where
buffer fills very slowly with new data to read for .NET/Xamarin
Defect ID: kaazing/tickets#118
Fixed an issue in cluster balancer service which prevented
servers to properly bind and unbind from the service.
Defect ID: kaazing/tickets#151
Fixed an out of memory issue on gateway server.
Defect ID: kaazing/tickets#109
Fixed StompMessageEncoder to avoid mutating the message
Defect ID: kaazing/tickets#116
Log contains exception stack messages "Early termination
of IO session" and "Network connectivity has been lost"
Defect ID: 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.
Defect ID: kaazing/tickets#103
Fixed an issue where durable subscriber clients fail to get
messages after varying lengths of time.
Defect ID: 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.
Comments