[asterisk-bugs] [JIRA] (ASTERISK-22614) Asterisk 12 using 308.000 handles with 60 open calls

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-22614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210676#comment-210676 ] 

Matt Jordan commented on ASTERISK-22614:
----------------------------------------

{quote}
It may mean that the CDR records are lost, the memory is not there, etc. I am afraid I am losing records and tons of money. Could somebody look into this?
{quote}

First, if you need support, I highly suggest you look to the asterisk-biz mailing list to contact interested developers in the Asterisk Developer Community. The issue tracker is not a place to solicit for support.

Second, did you actually deploy an alpha release for live customers?

Someone will look at this issue - but if you actually have a system deployed using an alpha release of Asterisk 12, then you should probably go back and re-read the [release announcement|http://lists.digium.com/pipermail/asterisk-announce/2013-August/000482.html].

{quote}
The first preliminary test release of Asterisk 12 is an alpha release, not a
beta release. Due to the size and scope of the changes in Asterisk 12, both an
alpha test cycle and a beta test cycle will be performed. While users are
encouraged to participate in both test cycles, users who choose to participate
in the alpha release testing should understand that an alpha release has not
undergone all of the community testing that a beta release goes through.
{quote}

In case that isn't clear, neither an alpha nor a beta release are production ready releases. That has never been the intent in any release of Asterisk, much less a [Standard release|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions] (which Asterisk 12 is) containing numerous architectural changes. Alpha and beta releases are done so that the community can help the Asterisk Developer Community test the release; not to deploy in situations where you may have live customers impacted.
                
> Asterisk 12 using 308.000 handles with 60 open calls
> ----------------------------------------------------
>
>                 Key: ASTERISK-22614
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22614
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 12.0.0-alpha1
>         Environment: Debian 7
>            Reporter: Private Name
>            Assignee: Private Name
>         Attachments: backtrace.txt, backtrace.txt, dialplan.txt
>
>
> My application crashes when it reaches 100 channels, and I just compiled it without optimization. With 67 opencalls,
>  lsof | grep asterisk|wc -l
> 308261
> but
> lsof -i | grep asterisk|wc -l
> 1024
> There is a huge handles leak. Even 1024 network handles for 68 calls is unheard of Another problem is that the command "core restart now" does not work, hangs forever. No new calls are accepted.
> I am not an engineer, so if somebody gracefully wants to log into my box, I will point the traffic to it. If nobody can help, I understand.
> But I think we can take advantage of my testing with lots of traffic, and this debug the app.
> If I compile Asterisk with "debug threads" the app never finishes loading.
> The amount of handles keeps going up, with the same amount of channels
> In 1/2 hour reaches
>  lsof | grep asterisk|wc -l
> 613388

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira