[asterisk-bugs] [JIRA] (ASTERISK-26111) stasis: Inactive Stasis app X missed message

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-26111:
-----------------------------------

    Summary: stasis: Inactive Stasis app X missed message  (was: Inactive Stasis app X missed message)

> stasis: Inactive Stasis app X missed message
> --------------------------------------------
>
>                 Key: ASTERISK-26111
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26111
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_stasis, Resources/res_stasis
>    Affects Versions: 13.8.0, 13.9.0, 13.9.1
>         Environment: OS: RedHat 7.2, kernel version 3.10.0-327.13.1.el7.x86_64
> Asterisk 13.9.1
>            Reporter: Claudiu Olteanu
>              Labels: stasis, user_events
>
> Sometimes when an application is unregistered at the WebSocket level (it was killed) and another one generates a user event to the inactive application, it receives an HTTP 204 response, instead of HTTP 404.
> Even though the server detects when the application that should receive the event is inactive and the message is missed, it doesn't notify the sender. 
> Therefore, the sender cannot detect that his message was missed. Moreover, if I list all Stasis applications, the one that was killed is still listed (after more than 20 minutes).
> I believe that it would be a good idea to notify the sender that the generated user event was missed and not handled with success. Otherwise, a Stasis application cannot detect when another one crashed and became inactive.
> To test it you can create a Stasis application, kill the process and try to generate a user event to that specific app.
> Thanks,
> Claudiu



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