With so many problems with spark, our user base has lost total confidence in jabber here.
none of the fixes seem to work, so it looks like we will be moving away from the spark client back to the old one. Its ashame as we were looking forward to using SSO (primary reason to move)
So the final list of problems, here are things that we just cant fix,
Spark sends duplicate messages (broadcasts and normal messges) 6 or 7 of the same message is common
If you type a message in the compose box, hitting return doesn’t make it appear in the top history window (history on/off in prefs dont change this)
windows dont flash when a message is recieved, again all setting checked nothing out of the ordinary
Cant group offline users in the broadcast window (nightmare to then send a message to include users off line)
Broadcast messages to offline users never arrive (a singula im to that user does andcan be read on next login)
Spark gradualy consumes RAM, dependant on how many messages/tabs are opened 15-20 tabs= 220MB ram average This ram doesnt release until the machine is rebooted, exiting spark doenst release the ram
Tested with v 2.5.6 & 2.5.7 same results.
for those that made suggestions, thanks for you help, We are staying with openfire as thats been great (although confidence is dented a little) WIll keep an eye on spark and may try it again one day. SSO would have bee nnice.
Sorry if its a bit of a rant, all the points are in other questions ive raised, just htought to put it in one place in case other users find this behaviour,