[asterisk-bugs] [JIRA] (ASTERISK-25083) Message.c: Message channel becomes saturated with frames leading to spammy log messages

[George Joseph (JIRA)]

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

George Joseph updated ASTERISK-25083:
-------------------------------------

    Target Release Version/s: 13.14.0

> Message.c: Message channel becomes saturated with frames leading to spammy log messages
> ---------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25083
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25083
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>            Reporter: Jonathan Rose
>            Assignee: Jonathan Rose
>            Severity: Minor
>      Target Release: 11.18.0, 13.4.0, 13.14.0, 14.0.0
>
>
> From the original report:
> >I see the messages (see attached) on the console and log after the server is running for a few days. The only way to clear them is to restart Asterisk. Then they come back a few days later. We have about 50 Digium D50's connected to this server.
> [2015-04-30 03:35:06] DEBUG[6922][C-00000000] channel.c: Soft-Hanging (0x20) up channel 'Message/ast_msg_queue'
> [2015-04-30 03:35:06] WARNING[6922][C-00000000] channel.c: Exceptionally long queue length queuing to Message/ast_msg_queue
> Message queue is clearly having frames queued on its read queue and is gradually becoming spammy, probably because the queue is gradually having more control frames and other special frames that aren't dealt with when flushing the queue due to having more than 128 frames in the queue. It's perfectly safe to just get rid of these frames routinely since they are never read by the Message channel anyway.



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