[asterisk-bugs] [Asterisk 0018028]: [patch] Exceptionally long queue length queuing to XXXXX
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Apr 19 12:20:39 CDT 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18028
======================================================================
Reported By: alecdavis
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18028
Category: Core/PBX
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: SVN
JIRA: SWP-2292
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!): 288195
Request Review:
======================================================================
Date Submitted: 2010-09-22 06:18 CDT
Last Modified: 2011-04-19 12:20 CDT
======================================================================
Summary: [patch] Exceptionally long queue length queuing to
XXXXX
Description:
Although this is under test conditions, this can go on for ever - seems
like 100's per second.
But the state of code at the moment, allows you to hangup, and it clears.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0017521 [patch] Brief lagginess on IAX2 channel...
related to 0018008 deadlock in local_bridgedchannel during...
related to 0018637 [patch] No MOH on Call Park and Excepti...
======================================================================
----------------------------------------------------------------------
(0133960) jcovert (reporter) - 2011-04-19 12:20
https://issues.asterisk.org/view.php?id=18028#c133960
----------------------------------------------------------------------
So prado, what was the theory behind the patch when it was applied, and
what is your theory about why it causes this problem, and finally, what
about the original problem this was supposed to fix?
It seems that if simply removing "ast_indicate(chan, -1);" from the
routine really does fix the problem, the right fix should be to determine
what ast_indicate is doing that's so bad and fix it there.
/john
Issue History
Date Modified Username Field Change
======================================================================
2011-04-19 12:20 jcovert Note Added: 0133960
======================================================================
More information about the asterisk-bugs
mailing list