THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#482 - deadlock if calling t_check_trans() from failure route User who did this - Andrew Pogrebennyk (marduk)

---------- Hi Daniel, that doesn't seem to cover the per-branch failure routes. E.g., I arm event route with t_on_branch_failure("redirect"); then in the event_route[tm:branch-failure:redirect] I'm checking the response code and if it's 302|301 append a new branch and go to some request route. If I call then t_check_trans() in that request route I'm still getting a deadlock. There is not much useful info that I can spot in the log file, e.g.: Nov 10 14:00:18 sp1 proxy[7887]: DEBUG: tm [t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T st art=0x7face3e057b8 Nov 10 14:00:18 sp1 proxy[7887]: DEBUG: tm [t_lookup.c:1144]: t_check_msg(): DEBUG: t_check_msg: T already found! ----------

More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=482#comment16...

You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.