Mysql driver leaking connections about ejabberd HOT 5 CLOSED

investigations and fix can be planed in January

from ejabberd.

We want a clean/stable 17.01
As we can reproduce error conditions in a test environment, possible fix will be injected in next beta, to come right after 17.01 release.

from ejabberd.

We'll need more time to validate possible fix works and does not break things, this will be delayed...

from ejabberd.

@mgpld: It has been solved?

from ejabberd.

Mysql driver leaking connections

I cannot reproduce that problem... or maybe I don't understand what exactly is the problem.

1. I setup ejabberd with two vhosts, one uses mnesia and the second vhost uses a mysql database for auth.

2. When ejabberd starts, it creates:
   A) an erlang process with p1_mysql_conn
   B) another erlang process with p1_mysql_recv, linked to A)
   C) a gen_tcp port linked to B)

3. Then I modify ejabberd configuration, so the second vhost no longer uses mysql database. And run: ejabberdctl reload_config

4. Then I check using erlang's Observer that A, B, and C are immediately closed.

from ejabberd.