we are running ejabberd on ubuntu and using http-polling for a flexible web front end. All is working as expected however every once in a while a client will disconnect (close pop up browser) and although we push a connection.disconnect() through JSJaC to the correct place, it won't really close the session. It's not always occurring, but does happen from time to time.
In short, I was wondering if their is some sort of configuration or something along those lines where I could have an account auto close it's session if no activity is present in the form of packet traffic or http-polling presence.
I haven't been able to track down any server side errors regarding the mystery "ghost sessions" the only clearly definitive clue I've been able to sniff out is the "replacement" of an active session upon an http-polling session being start from an account that's already "in session".
Thanks in advance.
P.S. upon reconnecting and disconnecting the session there is about a 25% chance that session won't even close when forcing a connection.disconnect() from Firebug or window.onunload