I see that there was some work done to the ASYNC module between 4.2.2 and 4.2.5
via Changelog...
commit bf8be8c52039fc50dafd0c9c140c01ab84384977
Author: Daniel-Constantin Mierla <mico...@gmail.com>
Date: Sun May 10 18:18:00 2015 +0200
tm: disabled use of dedicated mutex for async continue
- it can be enabled by defining ENABLE_ASYNC_MUTEX
- reply mutex is re-entrant and protects better the transaction
strucutre
- a dedicated lock for async continue exposes a race on removing from
timer when suspended transaction is resument at the same time when the
timer fires expiration event
I tried to just add a #!define ENABLE_ASYNC_MUTEX and the issue remains....
-----Original Message-----
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Alex
Balashov
Sent: Friday, June 12, 2015 4:27 PM
To: Aaron Hamstra
Subject: Re: [SR-Users] ASYNC Module
It is strange that you should see this change between minor point releases.
That does suggest a possible regression.
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Sent from my BlackBerry.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
