Re: Jabber Presence and Roster Issue - Client connections notclosing on database?

 charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300
X-Server: Indy SMTP Server
X-Library: Indy 9.00.10

 DeMena, Ronald wrote:
| 2nd Problem Description: 4 Users are using the Exodus 0.9.0.0 Client and
| lose their rosters every time they login and have to re-create them.
|
| Problem 1 appeared to take care of itself when I updated to JabberD
| 2.0s6 this morning.  The presence information between myself and several
| other users are working again the way we would expect such to.
|
| Problem 2 is not resolved.  At this time we have found that the rosters
| they generated before the JabberD update were not writing to the MySQL
| database.  Now after we flush the user information for the particular
| use from the database they write out again to the tables.  It appears to
| be independent of the client because if he uses another users client his
| list does not come up there either.
|
| I am curious what this bug is really about and if it causes a problem on
| the server:
| http://jabberstudio.org/projects/exodus/bugs/view.php?id=479

This bug is related to the jabberd 1.4 JSM module (mod_groups) which sent TWO
rosters to the client. Exodus was not handling the second set of roster items
correctly. This does not sound like the bug your seeing. I'm not sure how
laptops going to sleep or anything would affect folks loosing their rosters.
This seems more like a server side issue.

| It also appears that now any of our Exodus clients greater than 0.9.0.0
| can not use the JUD search tool now.
| But then again we only support 0.9.0.0 in our environment right now as
| our client software.

This was a bug in Exodus. The most recent daily builds
(http://exodus.jabberstudio.org/daily/) should work much better for doing
searches with JUD, etc.

pgm