Hi All, I've been looking into the changes made to res_odbc and the removal of connection handling. I can see that this change has been murged into the next release of Certified Asterisk. Would it be possible to regress this change until a sutible solution to the locking is found?
Kind regards, Ross On Mon, May 30, 2016 at 8:43 AM -0700, "Joshua Colp" <[email protected]<mailto:[email protected]>> wrote: Ross Beer wrote: > Hi, > > > I'm having an issue with the latest asterisk verison 13.9.1 and SVN MASTER: <snip> > > There are currently around 9 locks held and no phones are able to > register. The system is using the latest unixODBC and > mysql-connector-odbc drivers. This has been working well up until > recently. However a change appears to have been made to the way > endpoints are authenticated. I'm exploring the possibility that this may > be a unixODBC issue however I would be great full if anyone could offer > any assistance? A full backtrace[1] would be needed to see what is going on. You should also file an issue and link it here. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com<http://www.digium.com> & www.asterisk.org<http://www.asterisk.org> -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
