Presence changes are not being broadcasted to other connected resources


1) Log into the server from 2 different clients
2) Change the presence to away in one client
3) The other client should get a presence change notification

Step 3 is not hapenning.




February 29, 2008, 5:56 PM

Martin Drößler
May 21, 2007, 8:52 PM

The problem still exists in the current version.
When using LDAP, all contacts have subscription-status SUB_TO
but in org.jivesoftware.openfire.roster.Roster.broadcastPresence(Presence packet) the presence is only broadcasted
if (item.getSubStatus() == RosterItem.SUB_BOTH || item.getSubStatus() == RosterItem.SUB_FROM)

The best solution is to change the default subscription-status of LDAP-users to SUB_BOTH - or at least make it configureable.

Steve Smith
January 4, 2007, 8:47 AM

We (Atlassian) are still seeing this issue with Enterprise 3.1.1.

Les Bowen
June 23, 2006, 2:16 AM

Just did a little debugging... I am now in 3.0.0 beta, on OS X 10.4.6, with LDAP and MySQL.

Wildfire starts up without a hitch. Nothing unusual in debug or any other log files.

When the first user logs in, I get a bunch of output into debug, as the server looks through the LDAP setup and parses users and such. Nothing unusual. No errors.

Same goes for when the second user logs in. No errors, nothing unusual, other than the first user gets no presence notification. But this is not in the log files.

First user disconnects...

debug output is:

2006.06.22 13:07:49 Logging off <user>@<server fqdn>/<remote client id> on socket: 3acf34[SSL_RSA_WITH_RC4_128_SHA: Socket[addr=/<remote ip>,port=49227,localport=5223]] session: org.jivesoftware.wildfire.ClientSession@18c8ca status: 3 address: <user>@<server fqdn>/<remote client id> id: b97e019 presence:
<presence from="<user>@<server fqdn>/<remote client id>">
<x xmlns="vcard-temp:x:update">
<c xmlns="" node="apple:ichat:caps" ver="429" ext="avcap avavail maudio"/>
<x xmlns=""/>

Client is Apple iChat, but I get similar results from Spark.

I doubt this helps. If I can helps by debugging, I'm willing to help. I'm no developer by any means, but I know my way aroung a command line. So if there are any bugfizes for this, I'd be happy to help test them. Just let me know.

Sam Stainsby
June 9, 2006, 9:22 AM

Don't bother trying 2.6.1 .. I found exactly the same problem, at least with LDAP users/groups and group-based shared rosters.

Maybe time to switch back to ejabberd and suffer scripts and cron jobs to update the group-based rosters.



Gaston Dombiak


Gaston Dombiak