[asterisk-bugs] [JIRA] (ASTERISK-24701) Stasis: Write timeout on WebSocket fails to fully disconnect underlying socket, leading to events being dropped with no additional information

[Kevin Harwell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on ASTERISK-24701 started by Kevin Harwell.

> Stasis: Write timeout on WebSocket fails to fully disconnect underlying socket, leading to events being dropped with no additional information
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24701
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24701
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_stasis
>    Affects Versions: 13.1.0
>            Reporter: Matt Jordan
>            Assignee: Kevin Harwell
>
> By default, the Websocket connection to an ARI application has a write timeout of 100ms. That's kind of short, and in an especially busy system, you'll get a disconnect if the client fails to keep up with a burst of messages.
> The write timeout is configurable in {{ari.conf}}, so it can be bumped up. However, if a write timeout does occur, the following should happen:
> # The Websocket should be disconnected
> # {{res_stasis}} should be notified. A NOTICE should be displayed that a disconnect occurred.
> # When a Websocket reconnects for the application, at a minimum, it should receive the count of messages dropped since the last connection.



--
This message was sent by Atlassian JIRA
(v6.2#6252)