WebSockets: Missing CLOSE command after 'disconnect' command

Detail name	Value
Changelog Number	11058
Type	Bug
Status	Resolved
Affected Versions	Exasol 6.1.0, Exasol 6.2.0, Exasol 7.0.0
Fix Versions	Exasol 7.0.4, Exasol 6.2.12
Resolution Date	2020-11-16

Description

According to the 'disconnect' command documentation, the server should send CLOSE after receiving the 'disconnect' command to initiate closing the WebSocket network connection.

Due to the missing CLOSE command, client connections will remain open if the client does not close the connection itself.

Workaround:

Close the WebSockets connection explicitly on the client-side.

Fix

The database will send the CLOSE command after receiving a 'disconnect' command.

Changed behavior

Exasol will send the CLOSE control frame after receiving the 'disconnect' command to initiate closing the WebSocket connection.