getting weird \"timeout\" message...help???!!!

[j0sh]

$params["refresh_delay"] = 6000;
$params["timeout"] = 300000;

And the problem still occurs...

same here...

[Nelfo]

Nelfo, are you trying to login to your chat with the same nickname and with two different browsers

You may have found a separate issue, but I was having the disconnected issue while using only one browser which is why I tested it with a second.

[Nelfo]

In my opinion, this bug could be related to either performance or connection speed; I suppose this because in the phpfreechat I installed, some users can talk in the chat a whole day without any problems, whereas some users gets kicked systematicaly after 20 or 30 seconds...

This is intriguing. That would explain why I don't have the timeout issue on my dev environment (fast!) while in my temporary production environment (slow!) I'm having this problem with PFC....

[shini]

In my case I never experience timeouts with the computer I use at work, neither in dev environnement, nor in prod env. But if I try the chat on an old computer that runs javascript slowly (p3 773mhz), timeout occurs ...

hope this helps!

[j0sh]

In my case I never experience timeouts with the computer I use at work, neither in dev environnement, nor in prod env. But if I try the chat on an old computer that runs javascript slowly (p3 773mhz), timeout occurs ...

this is interesting... in effect i can chat normally on my pc but some users on my chat are kicked out every 20/30 seconds... probably it depends on user's ping?

[citricsquid]

I've found that it doesn't occur sometimes and others it does.
For example I've reinstalled the chat and configured it how i want and not a single timeout.
I guess it's to do with people logging out via. closing the browser window which doesn't, for some reason, end their sesssion.

So the server still thinks their online, so when they log in again it confuses the server and causes lots of timeouts.

[phpfreechat]

To help debugging this problem, it should be interesting to look at AJAX requests on the clients who timeout (using firebug for example). In fact, if the "quit (timeout)" message occurs it means that no AJAX request was done during the timeout period (timeout value is taken from the parameters, by default 20 seconds).
So maybe on slow PC with slow internet connection it can occurs ... maybe it can also occurs on special browsers versions ?

[j0sh]

(timeout value is taken from the parameters, by default 20 seconds)

i set a timeout of 200 seconds and the problem still occurs

[Nelfo]

To help debugging this problem, it should be interesting to look at AJAX requests on the clients who timeout (using firebug for example). In fact, if the "quit (timeout)" message occurs it means that no AJAX request was done during the timeout period (timeout value is taken from the parameters, by default 20 seconds).
So maybe on slow PC with slow internet connection it can occurs ... maybe it can also occurs on special browsers versions ?

I just logged into mine (Mac FF 2.0.0.12, though same happens in Safari) and the third Ajax response was simply:

Code: Select all

pfc.handleResponse('update', 'ok', '');

The first two were packed with data. It may also be worth mentioning that those first two requests took approx 600ms each.

[shini]

maybe it can also occurs on special browsers versions ?

At the beginning I thought it may be related to the browser version; but at the moment I think it's not, since all the users having trouble with the chat who tried different browsers did not solve the problem...

[shini]

I just tried to monitor ajax requests of the chat with firebug, and I noticed something that looks strange to me:

The first request send by the chat returned "pfc.handleResponse('update', 'ok', '');", but all the follwing requests returned a huge pack of data, in fact, the cache of the whole webpage...

Is it normal?

[shini]

some news?

[j0sh]

i changed to ajaxchat (http://blueimp.net/ajax/)
hope this helps

[Nelfo]

I don't want to switch, but I'd like to know if this problem is on the radar at least, so an update from the project founder would be appreciated.

[j0sh]

I don't want to switch, but I'd like to know if this problem is on the radar at least, so an update from the project founder would be appreciated.

i think this problem is critical... so i had to switch because my client can't wait yet