> It continues processing, but it never calls next_turn_phtable before
> exiting.
It technically *does* call next_turn_phtable, but on a *new* presentity in the
phtable. It does not increment the current_turn on the same presentity that it
updated last_turn on. This causes a mismatch on that presentity going forward.
> This will cause the process to lockup forever, waiting for its turn, on the
> next publish received.
Specifically, both of the processes in this scenario will continue on their
way. The *next* publish to the original presentity will lock, because
current_turn is less than last_turn, and nothing exists to increment it.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/754#issuecomment-171401097
_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
