I realized that I should send this info to sipx-users, as it is relevant to people who are using the unstable, "development" versions of sipX, even if they aren't involved in development.
I've added a section to sipx-snapshot to record information which is useful for detecting deadlocks. Deadlock problems are rare, but when they happen, they freeze part of the sipX system, often in very odd ways. Deadlocks always can be cleared by restarting sipX, but they are difficult to diagnose from what is recorded in the log files. The additions to sipx-snapshot can help, if the snapshot is done before sipX is restarted, and the deadlock is still present. The visible consequences of this improvement are that sipx-snapshot will take 15 to 30 seconds longer than it has previously, and it will interrupt the execution of each process for a few seconds. Unfortunately, this interruption might cause a few calls to fail, although if the user retries the operation, the second attempt should work as expected. I don't expect any other problems, but if anyone sees any problem (especially if sipx-snapshot hangs), please send mail to sipx-users. Of course, users of the stable (3.8 and 4.0 versions) won't see any of these changes, they are only being tested in the 4.1 versions. Thanks, Dale _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
