ERR 004, BAD_SESSID after long connection

[Mike]

After a few hours of staying connected, I'm getting an error 004
(BAD_SESSID). We are using it for a chat environment, so a few hours
isn't that long. It doesn't seem to matter if there is a lot of
activity or a litte, we get this pretty frequently. There are about
300 people connected at once to the server and it happens 2-3x per day
for a handful of users.

Any ideas?

[Rik Keppel]

Try checking the cookies of APE from those users. With checking, I
mean comparing them every now and then. Maybe displaying them and/or
keeping them in php session variables to compare? Just some ideas to
get you started ; )

[Mike]

Ok, it isn't the cookies. Here is the last valid one:

Content-type:application/x-www-form-urlencoded; charset=UTF-8User-
Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/
534.52.7 (KHTML, like Gecko) Version/5.1.2 Safari/534.52.7X-Requested-
With:XMLHttpRequestForm [{"cmd":"CHECK","chl":
59,"sessid":"d9ef4d6c537539638ca1bb544f02bad3"}]:

As you can see the sessid and chl are set and everything is fine with
that. Then this one:

[{"cmd":"CHECK","chl":
60,"sessid":"d9ef4d6c537539638ca1bb544f02bad3"}]:

Which returns fine.

Then the last post: [{"cmd":"CHECK","chl":
61,"sessid":"d9ef4d6c537539638ca1bb544f02bad3"}]
and it returns this:
[{"time":"1325112408","raw":"ERR","data":
{"code":"004","value":"BAD_SESSID"}}]

along with response headers:
Pragma: no-cache
Content-Type: text/html
Cache-Control: no-cache, must-revalidate
Expires: Thu, 27 Dec 1986 07:30:00 GMT