|Summary:||ASTERISK-08751: [patch] reloading a keyword e.g. "extconfig" prevents further reloads|
|Reporter:||Ben Smithurst (bsmithurst)||Labels:|
|Date Opened:||2007-02-08 05:24:00.000-0600||Date Closed:||2007-02-08 07:50:47.000-0600|
|Environment:||Attachments:||( 0) reload.patch|
|Description:||It appears that a command like "reload extconfig" leaves the reloadlock mutex held, and any subsequent reload commands give the usual "previous reload didn't finish" error. This applies to reloading the reload_classes names, not an actual module name (blah.so or whatever).|
However this doesn't always happen. It appears that doing another reload on the same CLI session will succeed, however a reload on another session will fail, perhaps because on the same session the thread already holds the lock, and so the trylock succeeds?
The attached patch would appear to be a sensible fix anyway, I think.
|Comments:||By: Ben Smithurst (bsmithurst) 2007-02-08 05:48:03.000-0600|
patch taken from 1.4.0 but applies to trunk too.
By: Tilghman Lesher (tilghman) 2007-02-08 07:50:47.000-0600
Fixed in 53532, 53533.