[Asterisk-Dev] Re: [Asterisk-biz] cdr_addon_mysql.c and 1.0.7==DEADLOCK

[Bob Goddard]

On Saturday 26 March 2005 20:02, Brian West wrote:
> Just make a call... you'll deadlock/block the moment it tries to insert
> a record.
[... Next time delete the old signatures and don't top post ...]

I have no problem here running 1.0.7 and inserting CDR records
into MySQL.


B

> On Mar 26, 2005, at 9:05 AM, Greg Boehnlein wrote:
> > On Sat, 26 Mar 2005, Tony Mountifield wrote:
> >
> > [deleted]
> >
> >> That's very strange, because cdr_addon_mysql.c hasn't changed in
> >> Stable
> >> since v1.0:
> >>
> >> [root at softins asterisk-addons]# cvs log cdr_addon_mysql.c
> >>
> >> RCS file: /usr/cvsroot/asterisk-addons/cdr_addon_mysql.c,v
> >> Working file: cdr_addon_mysql.c
> >> head: 1.7
> >> branch:
> >> locks: strict
> >> access list:
> >> symbolic names:
> >>         v1-0-7: 1.5
> >>         v1-0-6: 1.5
> >>         v1-0-4: 1.5
> >>         v1-0: 1.5.0.2
> >>         v1-0-1: 1.5
> >> keyword substitution: kv
> >> total revisions: 7;     selected revisions: 7
> >> ...
> >>
> >> I'll try it here, too. Any information on whether the deadlock happens
> >> every time, or only sometimes, etc?
> >
> > Just because it hasn't changed doesn't mean that a new deadlock
> > situation
> > can't be discovered! ;)
> >
> > Forging on, what is the nature of the deadlock situation? How can it be
> > reproduced?