[asterisk-bugs] [Asterisk 0014253]: app_voicemail leaves sockets in close wait.
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Feb 2 15:30:47 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14253
======================================================================
Reported By: Skavin
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14253
Category: Applications/app_voicemail/IMAP
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.4.21.1
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-01-15 15:23 CST
Last Modified: 2009-02-02 15:30 CST
======================================================================
Summary: app_voicemail leaves sockets in close wait.
Description:
app_voicemail is not closing imap sockets and they are going into
CLOSE_WAIT.
I am using imap-2006j
open files seem to go up during busy times but never drop.
my asterisk-vm process does not notify it is only there to isolate
recording and playback of voice mail from the rest of asterisk.
my asterisk process forwards to asterisk-vm in the case of busy/noanswer
or checking voicemail.
in 50 hours I have generated
836 handles in CLOSE_WAIT all to imap
33 handles in ESTABLISHED 1 mysql 32 imap
12 udp handles
======================================================================
----------------------------------------------------------------------
(0099277) Corydon76 (administrator) - 2009-02-02 15:30
http://bugs.digium.com/view.php?id=14253#c99277
----------------------------------------------------------------------
Okay, on further examination, it appears that the IMAP support in
app_voicemail is one huge resource leak, which cannot be easily remedied.
It engages in sharing of resources, migration of multiple pointers which
are copied between structures, etc. It's clear from the implementation
that this was done for the purpose of making IMAP support very fast.
Unfortunately, the code also leaks like a sieve. In fact, the way it's
written, I'm surprised that it doesn't constantly blow up.
Issue History
Date Modified Username Field Change
======================================================================
2009-02-02 15:30 Corydon76 Note Added: 0099277
======================================================================
More information about the asterisk-bugs
mailing list