Max_inactivity for http-bind is longer than value in config

Hi,
I'm currently using ejabberd-2.1.6 and I have 30 seconds set as the max_inactivity so that ejabberd will close their session. This works for about 40% of users.

But for certain sessions, the timeout for inactivity is anywhere from 80 seconds to 90 seconds.

Is there another module option or macro that has to be redefined?

What could be causing the higher timeout for close session?

- Thanks

Could someone please help

Could someone please help with this issue?

Thank you,
Man

mhoang wrote: Hi, I'm

mhoang wrote:

Hi,
I'm currently using ejabberd-2.1.6 and I have 30 seconds set as the max_inactivity so that ejabberd will close their session. This works for about 40% of users.

But for certain sessions, the timeout for inactivity is anywhere from 80 seconds to 90 seconds.

What could be causing the higher timeout for close session?

Notice that inactivity is defined as "user receives and sends nothing". Maybe some users don't send, but receive stuff, so their session keeps alive more than 30 seconds?

mhoang wrote:

Is there another module option or macro that has to be redefined?

An additional way to close sessions when the client doesn't exist is mod_ping:
http://www.process-one.net/docs/ejabberd/guide_en.html#modping

Syndicate content