[SOLVED] Annoying problem after update to 5.0.9

[tgx]

We are using Spark to access the Zimbra IM subsystem.
After upgrading Zimbra from 5.0.6GA_FOSS to 5.0.9 Spark
now seems to log users out for inactivity. As a result
there is a constant chiming and visual clue that users are
getting dropped off repeatedly. Was there a tweak
that was made to the IM system that I can untweak?

Thanks.

***Additional info: The timeout is exactly 10 minutes.**

[tgx]

Can someone at least point me to where you configure this service?
There isn't a lot left from its Jive roots so their support base doesn't
help much.

[tim brennan]

This is definitely a new behavior in 5.0.9. I've filed Bug 31292 on it.

Add yourself to the CC list for the bug. I will post workaround if I can find one.

[tgx]

FWIW the whole IM system seems to be botched.
I am seeing the same behavior using the Zimbra web interface.
Constant presence updates. As a temporary work around I have disabled
presence notifications. While that works for the web interface it does not
propogate down to the Spark clients. Also, after 15 or so minutes the Spark
client will completely disconnect saying it has closed the connection due
to an error.

I may have to consider rolling back.

***UPDATE*** Disabling the presence notification does not help.

[tgx]

This is definitely a new behavior in 5.0.9. I've filed Bug 31292 on it.

Add yourself to the CC list for the bug. I will post workaround if I can find one.

Thanks. I'll keep posting if I discover anything new.

[tgx]

One other item,
There is a setting in the Preferences/Instant Messaging tab of the Zimbra web client that references a default 10 minute timeout. However changing that setting has had no effect. It's the only place I was able to find a reference to any value of 10.

[tgx]

Posting here for others.

----------------------------
workaround for 5.0.9 (this is fixed in 5.0.10) is to go into
/opt/zimbra/conf/localconfig.xml and add a new entry for the
'xmpp_client_idle_timeout' key with a large value.

The value is in msec, the default is 600000 (10 minutes). Make it 100 minutes,
or 1000 minutes to lessen the annoyance to users.

Note that raising this value will lower the rate at which the server recovers
some memory when clients drop connections. Make sure you change it back after
you upgrade to the fixed version.
--------------------------

Full details: Bug 31292 – XMPP client connections timing out after 10 minutes