Invites to group chats - inconsistent issues

We are seeing inconsistencies with group chats invites. Several MacOS 10.4 users don’t get any invite at all, and all users don’t see the initial invitation text.

Our Mac 10.5 leopard users and Linux Pigeon users do not seem to have the inconsistency issue, but all users don’t see the initial invite text.

Anyone else experiencing these issues? Any ideas how to fix?

Server: MacOS X 10.5.6 client

Clients with issues: iChat Mac OS X 10.4

often with Chax installed

OpenFire: 3.6.3

configured using LDAP from OSX

Thanks.

Upon researching this issue, I believe the proper phrasing for this problem might be:

presence status for group chats

is there a location to edit these parameters?

Here’s the log files from the client machine that does not recieve the invitation:

2009-02-17 08:37:33.549 iChatAgent[263] WARNING: JabberMessageNode: ignoring unknown child http://jabber.org/protocol/pubsub#event*event
2009-02-17 08:37:33.549 iChatAgent[263] WARNING: JabberMessageNode: ignoring unknown child http://jabber.org/protocol/address*addresses
2009-02-17 08:37:33.549 iChatAgent[263] WARNING: JabberMessageNode: Couldn’t parse date '2009-02-16T18:24:18.188Z’
2009-02-17 08:37:33.584 iChatAgent[263] WARNING: JabberMessageNode: ignoring unknown child http://jabber.org/protocol/pubsub#event*event
2009-02-17 08:37:33.584 iChatAgent[263] WARNING: JabberMessageNode: ignoring unknown child http://jabber.org/protocol/address*addresses
2009-02-17 08:37:33.584 iChatAgent[263] WARNING: JabberMessageNode: Couldn’t parse date '2009-02-17T16:29:14.112Z’
2009-02-17 08:37:33.584 iChatAgent[263] WARNING: JabberMessageNode: ignoring unknown child http://jabber.org/protocol/pubsub#event*event
2009-02-17 08:37:33.584 iChatAgent[263] WARNING: JabberMessageNode: ignoring unknown child http://jabber.org/protocol/address*addresses
2009-02-17 08:37:33.584 iChatAgent[263] WARNING: JabberMessageNode: Couldn’t parse date '2009-02-04T22:50:48.130Z’
2009-02-17 08:37:33.584 iChatAgent[263] WARNING: JabberMessageNode: ignoring unknown child http://jabber.org/protocol/pubsub#event*event
2009-02-17 08:37:33.584 iChatAgent[263] WARNING: JabberMessageNode: ignoring unknown child http://jabber.org/protocol/address*addresses
2009-02-17 08:37:33.584 iChatAgent[263] WARNING: JabberMessageNode: Couldn’t parse date '2009-02-13T00:16:57.653Z’
2009-02-17 08:37:33.585 iChatAgent[263] WARNING: JabberMessageNode: ignoring unknown child http://jabber.org/protocol/pubsub#event*event
2009-02-17 08:37:33.585 iChatAgent[263] WARNING: JabberMessageNode: ignoring unknown child http://jabber.org/protocol/address*addresses
2009-02-17 08:37:33.585 iChatAgent[263] WARNING: JabberMessageNode: Couldn’t parse date '2009-02-16T19:15:49.783Z’
2009-02-17 08:37:33.597 iChatAgent[263] WARNING: JConnection: Couldn’t find target for IQ of type get containing ‘jabber:iq:last*query’ ID 'purple2fe07248’
2009-02-17 08:38:06.606 iChat[260] CFLog (21): dyld returns 2 when trying to load /Library/Contextual Menu Items/TerminalHerePlugin.plugin/Contents/MacOS/TerminalHerePlugin
2009-02-17 08:38:06.607 iChat[260] CFLog (22): Cannot find function pointer TerminalHerePluginFactory for factory 9185D7B4-BAFE-11D6-A6CB-000393A580D4 in CFBundle/CFPlugIn 0x173af180 </Library/Contextual Menu Items/TerminalHerePlugin.plugin> (bundle, not loaded)
OMC->ReadPreferences: invalid command description format version number

This is the specific log entry that appears after another user tries to initiate an invitation:

2009-02-17 08:39:01.779 iChat[260] *** Assertion failure in -[ActiveChat initWithMessage:style:], /SourceCache/iChat/iChat-446/Source/Model/Chat.m:714

Anyone else unable to send invites to MacOS X 10.4 iChat users?

for all those folks on the edge of your seats on this issue.

here’s our server error log, regarding LDAP. i’ve tried to reset the group to no avail…

2009.02.23 09:25:37 [org.jivesoftware.openfire.ldap.LdapGroupProvider.getGroup(LdapGroupProvider.ja va:91)]
org.jivesoftware.openfire.group.GroupNotFoundException: Groupname Luma Jabber not found
at org.jivesoftware.openfire.ldap.LdapManager.findGroupDN(LdapManager.java:855)
at org.jivesoftware.openfire.ldap.LdapManager.findGroupDN(LdapManager.java:782)
at org.jivesoftware.openfire.ldap.LdapGroupProvider.getGroup(LdapGroupProvider.jav a:83)
at org.jivesoftware.openfire.group.GroupManager.getGroup(GroupManager.java:278)
at org.jivesoftware.openfire.group.GroupManager.getGroup(GroupManager.java:257)
at org.jivesoftware.openfire.group.GroupCollection$UserIterator.getNextElement(Gro upCollection.java:103)
at org.jivesoftware.openfire.group.GroupCollection$UserIterator.hasNext(GroupColle ction.java:66)
at org.jivesoftware.openfire.roster.RosterManager.getSharedGroups(RosterManager.ja va:162)
at org.jivesoftware.openfire.roster.Roster.(Roster.java:105)
at org.jivesoftware.openfire.roster.RosterManager.getRoster(RosterManager.java:86)
at org.jivesoftware.openfire.user.User.getRoster(User.java:368)
at org.jivesoftware.openfire.handler.IQRosterHandler.manageRoster(IQRosterHandler. java:200)
at org.jivesoftware.openfire.handler.IQRosterHandler.handleIQ(IQRosterHandler.java :105)
at org.jivesoftware.openfire.handler.IQHandler.process(IQHandler.java:49)
at org.jivesoftware.openfire.IQRouter.handle(IQRouter.java:351)
at org.jivesoftware.openfire.IQRouter.route(IQRouter.java:101)
at org.jivesoftware.openfire.spi.PacketRouterImpl.route(PacketRouterImpl.java:68)
at org.jivesoftware.openfire.net.StanzaHandler.processIQ(StanzaHandler.java:319)
at org.jivesoftware.openfire.net.ClientStanzaHandler.processIQ(ClientStanzaHandler .java:79)
at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:284)
at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:176)
at org.jivesoftware.openfire.nio.ConnectionHandler.messageReceived(ConnectionHandl er.java:133)

Does anyone know if there is a way to resubmit this query since there are no suggestions for fixes?