[asterisk-bugs] [JIRA] (ASTERISK-28433) More than 1 AMI connection ends up dying

[Chris Savinovich (JIRA)]

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

Chris Savinovich updated ASTERISK-28433:
----------------------------------------

    Assignee: Luke Escude
      Status: Waiting for Feedback  (was: Triage)

Hello Luke, did you just say the issues on the second AMI login start about one full day after it's been connected? If so, I can think of a few reasons why things start going funny if you maintain an open connection that long. I would recommend you insert in your client code logic to send "keep alives" every x seconds.  Having said that, why would you want to maintain an AMI connection open that long? The efficient way to use AMI is to login send the request, get the response and logoff.  If you need to capture events then ARI is much better precisely because of its stateless nature.
Let us know if your issue persists even after taking the above measures.
Thanks


> More than 1 AMI connection ends up dying
> ----------------------------------------
>
>                 Key: ASTERISK-28433
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28433
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 16.3.0
>         Environment: CentOS 7 x64
>            Reporter: Luke Escude
>            Assignee: Luke Escude
>            Severity: Minor
>
> I'll need some help figuring out a proper diagnostic approach to help you guys out, since I don't have any ideas on how to recreate the issue consistently with valuable results. Anyways...
> With a single AMI connection, the connection lasts forever - Ping, various commands, etc. the pipe never dies.
> As soon as a second AMI connection forms to asterisk, it doesn't seem to survive - Meaning a Ping command (and all other commands) will suddenly stop returning any data. But, the socket doesn't seem to die.
> A secondary issue is that some Originate commands will cause the AMI socket pipe to completely lock up for 10 seconds+ but I'd rather solve this issue first.
> Any ideas on how to learn more details? The second AMI connection can typically last about a day, then drops off.
> Interestingly, running 'manager show connected' after the second connection drops causes ALL further asterisk CLI output to not exist - The CLI will no longer push any information to the screen until you exit then re-enter the CLI again.



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