<br><div class="gmail_quote">On 6 February 2012 10:45, Jonas Kellens <span dir="ltr"><<a href="mailto:jonas.kellens@telenet.be">jonas.kellens@telenet.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<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><div><br></div><div>Regards,</div><div>Steve.</div>
</div>