Connection close event is executed from TCP main process, which likely has no 
SQL connection open. Till some point in the past, connection close event was 
triggered from a few places (from tcp worker processes), but actually it was 
not done for all cases when the connections were closed, some of these events 
missing (there are situations when only tcp main process close the connections).

Now, I would strongly advise doing anything time expensive in the TCP main 
process, it was designed only as tcp connections manager, so in this case, I 
would rather delegate the sql query to an async worker (via async module or via 
mqueue+rtimer).



-- 
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3843#issuecomment-2098023946
You are receiving this because you are subscribed to this thread.

Message ID: <kamailio/kamailio/issues/3843/2098023...@github.com>
_______________________________________________
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org

Reply via email to