One thought on - One Thread Per Peer

• I would hazard a guess to say that all three of your e-mails [1] [2]
  (and this one) are the same problem. As such, I’ll reply to this thread and not the others.

  Without seeing what in particular those threads are doing are how you got the system into that state, it’s impossible to say whether or not the behaviour is expected. A few questions then:
  1) Can you provide a scenario that reproduces this reliably? A sip configuration (with a single peer) that results in a thread
  ‘lingering’ longer than anticipated would help to determine what is happening.
  2) Can you get a thread capture using gdb of a running Asterisk process? That will inform us what the threads are actually doing when this occurs. You can get instructions for getting a gdb backtrace from the wiki [3], although the following should suffice:

  # gdb -ex “thread apply all bt” –batch /usr/sbin/asterisk `pidof asterisk` > backtrace-threads.txt

  Thanks –

  Matt

  [1] http://lists.digium.com/pipermail/asterisk-users/2014-November/285083.html
  [2] http://lists.digium.com/pipermail/asterisk-users/2014-November/285084.html
  [3] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace