I was very happy when I noticed new 2.0 version because this chat modul has very friendly UI and looks exactly to fits my needs (flag friend integration and sound notification when a new message arrive). I have installed 2.0-beta2 version, and configured all settings.

Unfortunately after few cache clears site goes down with MySQL database connection error: "Too many connections". Issue is repeating every 5-10 minutes. Ajax pulling method did not work at all. When chat modul is disabled, everything is fine (site is alive all the time).


Were you able to install the module properly? Did you upgrade it from an earlier version? What is the value of the max_connections variable in the mysql configuration file?

No, I was not able to clean install beta-2 version, so I installed version 1.2 and upgraded to beta-2.

mysql.allow_persistent On

mysql.max_links Unlimited

mysql.max_persistent Unlimited

Version:6.x-2.0-beta2» 6.x-2.0-beta4

Uninstall (not just disable) and install the drupalchat 6.x-2.0-beta4. Also read this issue - #1055896: Many issues one after another... FAQ & Help here! for installation related problems.

This error happens also with the drupal 7 version

Priority:Normal» Critical

I have the same problem, this module exhausted server resources.

Version:6.x-2.0-beta4» 6.x-2.x-dev

Version:6.x-2.x-dev» 6.x-2.0-beta4

Same problem here using the 6.x-2.0-beta4.

I noticed a considerable performance loss over the course of the day when developing a site on a single-site dedicated server setup. The site became more and more sluggish over the day. Disabling drupalchat instantly resolved the issue..
MySQL version used is 5.1.49. max connections allowed is set to 1.100.
Looking at the server stats, the db has set up
262 k connections and processed
3 M select and 3 M update queries
over the last 24 days, on a single site dev machine! That seems too many... I'll see how many I get now that the module is disabled..

Plan to integrate this module with nodejs. That should fix this issue.

It sounds very good. I thought already that nobody cares about this handy module.

I stopped to use this because this bug (drupal 6.x version), and start to use bowob chat instead, which is as well very handy, but looking forward to try this again and maybe replace bowob with this in the future (if here will be the maintaince for this project).

maybe this can be helpful

Yes, I am working on integration with this module.

Version:6.x-2.0-beta4» 7.x-1.x-dev

Good new: DrupalChat 7.x-1.x-dev now supports node.js backend! :-)
Commit: http://drupalcode.org/project/drupalchat.git/commit/15b37f6

these are very good news! looking forward to 6.x :)

Im guessing I would need this module, node js integration module.. and do I have to upload something for node.js (sorry if this sounds stupid.. I know more about design than programing)

for drupal 6, is there a solution?

this module can reduce the ajax time:

And a backport do D6 is comming at Node.js module:

I'm lost comparing D7/D6 versions of both modules...can someone help with the steps for suport it in d6?


Version:7.x-1.x-dev» 6.x-2.x-dev

Subscribing DrupalChat 6.x with Node.js

Subscribing DrupalChat 6.x with Node.js

I was excited to find a currently supported live chat module for my small business site and got DrupalChat (drupalchat-6.x-2.0-beta11.tar.gz) installed and working for support communication with our clients ... I thought. Then while testing out DrupalChat, my site, hosted on a large shared hosting service, popped up an error saying it has a problem and is offline. The ONLY way I could recover was to delete the sites/all/modules/drupalchat directory. I am guessing I am going to get a nasty e-mail from my web host about too much SQL usage again if this "Too many connections" error was what caused my site to tank.

A useful, "free", chat module seemed too good to be true. It turned out it was too good to be true for us anyway. :(

In Drupal 7 it appears to be keeping mysql connections open. If I disable the module and wait for the hung connections to clear, I can wander all over the site and no problem. If the module is re-enabled, the hung connections return suggesting the callback used is terminating it such a way that it prevents Drupal from cleaning up the database connection.

This may be happening due to long polling. Could you please switch to normal ajax and see if it works fine? If so, then I will change default polling method to Normal AJAX. Thanks.

Initial test shows Normal AJAX is working better. Will need to run longer test tomorrow.


So far, using the Normal AJAX method there are no signs of hung mySql connections so this would seem to be a better default.

Thanks a lot for confirming this. Will make it the default in next release.

Version:6.x-2.x-dev» 7.x-1.x-dev

Change introduced in 7.x-1.0-beta17. Thanks.