Yes it's mySQL and Smack client

subhamoy — Thu, 18 Dec 2008 15:44:11 +0000

Yes we are using mySQL, but setting the odbc_keepalive_interval parameter to 15 minutes didn't help. We have not tried the odbc_start_interval parameter yet.
However we are using Smack client API to connect to ejabberd and we made the following changes marked between the comments in our connection creation:

XMPPConnection con = null;
try {
con = new XMPPConnection(SERVER_ADDRESS, SERVER_PORT);
con.login(loginId, loginPwd, session.getId());
} catch (XMPPException xmppe) {
xmppe.printStackTrace();
// added the following fix
if (con != null) {
con.close();
}
// end addition
}

We are using a slightly older version of Smack from Jive, which does not have the explicit con.connect() API supported by later versions.
We are assuming Smack creates an unlogged in connection every time "new XMPPConnection()" is called and it needs to be closed if login fails. If there are too many login failures ejabberd might have many unlogged in connections open and that is not allowing any more login connections. We had many login failures at our site and that is why we tried this fix, though we can say whether it would work only after observing for few more days.

Any other ideas would be welcome.

Thank you very much for your help.

You didn't mention, but it

mfoss — Mon, 15 Dec 2008 11:11:31 +0000

You didn't mention, but it seems you use MySQL for authenticating users, right?

Maybe the message means that the connection to the MySQL server was closed. Who and why closed it? It may be ejabberd, or your server, or TCP due to inactivity.

You can try different values of options odbc_keepalive_interval and odbc_start_interval, maybe that helps to solve your problem. Check the ejabberd Guide for documentation of those options.

ejabberd - Comments for "Authentication failing for all users"

Yes it's mySQL and Smack client

You didn't mention, but it