[Asterisk-Dev] deadlock with realtime

[Matthew Boehm]

You have a debug core trace? Can't help you without one.

Yes, locks are necessary for each query because the mysql connection is
shared amoungst all realtime queries. The thread must have control of the
resource when it does its thing otherwise unknown stuff would happen.

-Matthew


> From: fcbouan <fcbouan at frontier.fr>
> Reply-To: Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
> Date: Fri, 13 May 2005 15:05:44 +0200
> To: <asterisk-dev at lists.digium.com>
> Subject: [Asterisk-Dev] deadlock with realtime
> 
> hi,
> i work on last asterisk CVS version. i use a custom module based on
> cdr_addon_mysql.c.
> 
> On last CVS version and realtime, asterisk got deadlock with ast_mutex_lock
> used for mysql query. is there some asterisk lock/unlock change on recent CVS
> upgrade or Realtime ? i check realtime source there nothing special.
> 
> I remove all lock/unlock in my file but i got deadlock. Is mutex_lock must be
> used  with mysql (INSERT, SELECT) ?
>  
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev