<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 02/06/2012 12:14 PM, Steve Davies wrote:
<blockquote
cite="mid:CAFLM+hv2HsEmUvUEPSt2_GuVYUmw-cXjFhtRkU-ZKjwewTXVWQ@mail.gmail.com"
type="cite"><br>
<div class="gmail_quote">On 6 February 2012 10:45, Jonas Kellens <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:jonas.kellens@telenet.be">jonas.kellens@telenet.be</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"> <font face="Helvetica,
Arial, sans-serif">Hello,<br>
<br>
is there anyone that can give me some more information on
these "deadlocks" ?!<br>
<br>
How can these deadlocks occur and what is "good practise"
to avoid these problems ??<br>
<br>
<br>
Jonas.<br>
<br>
</font></div>
</blockquote>
<div><br>
</div>
<div>The only way to avoid deadlocks is to report them when they
happen, provide the requested debug, and hope for a fix.</div>
<div><br>
</div>
<div>Deadlocks are just a type of bug. Nothing you can do to
avoid it unless you can work out the events that lead up to
it, and avoid doing that.</div>
<div><br>
</div>
<div>I am still using 1.6.2.22 in many places, and if I see a
deadlock "show locks" trace on the mailing list - I will
certainly be looking into it.</div>
<br>
</div>
</blockquote>
<br>
I am not sure if "show locks" will give me any output, because the
Asterisk CLI is unresponsive... Haven't tried it thought.<br>
<br>
Can I then act upon the information that "show locks" gives me ? Is
there some other command to "unlock" the Channels that produce the
lock ??<br>
<br>
<br>
Kind regards,<br>
Jonas.<br>
</body>
</html>