We're updating the issue view to help you get more done. 

Joining new MUC room results in a 404 error

Description

The largest is, after I upgraded to 3.9.2, anyone
attempting to join a MUC that was not created on the server gets a 404
error. I had to recreate every MUC by hand via the console just to get them
working.

Environment

None

Acceptance Test - Entry

None

Activity

Show:
Steve R.
September 29, 2014, 8:01 PM

We are seeing this issue with 3.9.3 as well.

We are using a plugin to create the MUC from our software. The plugin has no issue and the room looks fine in the OpenFire UI. However, whenever we try to connect to the group chat, whether from our code, Pidgin or PSI, then we receive the 404. If I delete the group chat in OpenFire, and recreate with the same name, then it works fine.

Our setup:

  • Using the embedded DB.

  • Using a custom group chat setting object.

  • Using BOSH connections.

  • Using the 'User Service' plugin to create the group chat.

  • Running on Windows.

We've tried to modify a group chat that was created by the plugin and re-save it, but that did not correct the issue.

We also exported the a working and non-working group chat, using the plugin, but did not see any difference in the attributes. The first item below is failing, but the second succeeds.

<chatRooms>
<chatRoom>
<roomName>ps_cefcb942-0aab-44bd-9a0b-69abec6fdf38</roomName>
<naturalName>ps_cefcb942-0aab-44bd-9a0b-69abec6fdf38</naturalName>
<description>PS_cefcb942-0aab-44bd-9a0b-69abec6fdf38-update</description>
<creationDate>2014-09-25T19:03:40.808Z</creationDate>
<modificationDate>2014-09-29T15:38:54.043Z</modificationDate>
<maxUsers>10</maxUsers>
<persistent>true</persistent>
<publicRoom>true</publicRoom>
<registrationEnabled>true</registrationEnabled>
<canAnyoneDiscoverJID>false</canAnyoneDiscoverJID>
<canOccupantsChangeSubject>false</canOccupantsChangeSubject>
<canOccupantsInvite>false</canOccupantsInvite>
<canChangeNickname>false</canChangeNickname>
<logEnabled>true</logEnabled>
<loginRestrictedToNickname>false</loginRestrictedToNickname>
<membersOnly>false</membersOnly>
<moderated>false</moderated>
<broadcastPresenceRoles>
<broadcastPresenceRole>participant</broadcastPresenceRole>
<broadcastPresenceRole>visitor</broadcastPresenceRole>
</broadcastPresenceRoles>
<owners>
<owner>managementacct@xxx.yyy.net</owner>
</owners>
<admins />
<members />
<outcasts />
</chatRoom>
<chatRoom>
<roomName>ps_8063f44e-dfca-46ae-89d4-fc3c4408c627</roomName>
<naturalName>PS_8063f44e-dfca-46ae-89d4-fc3c4408c627</naturalName>
<description>PS_8063f44e-dfca-46ae-89d4-fc3c4408c627</description>
<creationDate>2014-09-28T13:46:11.857Z</creationDate>
<modificationDate>2014-09-28T13:46:11.878Z</modificationDate>
<maxUsers>10</maxUsers>
<persistent>true</persistent>
<publicRoom>true</publicRoom>
<registrationEnabled>true</registrationEnabled>
<canAnyoneDiscoverJID>false</canAnyoneDiscoverJID>
<canOccupantsChangeSubject>false</canOccupantsChangeSubject>
<canOccupantsInvite>false</canOccupantsInvite>
<canChangeNickname>false</canChangeNickname>
<logEnabled>true</logEnabled>
<loginRestrictedToNickname>false</loginRestrictedToNickname>
<membersOnly>false</membersOnly>
<moderated>false</moderated>
<broadcastPresenceRoles>
<broadcastPresenceRole>participant</broadcastPresenceRole>
<broadcastPresenceRole>visitor</broadcastPresenceRole>
</broadcastPresenceRoles>
<owners>
<owner>managementacct@xxx.yyy.net</owner>
</owners>
<admins />
<members />
<outcasts />
</chatRoom>
</chatRooms>

Roman
October 1, 2014, 1:12 PM

@Steve Please update to MUC Service Plugin 0.2.3. That should fix your problem.

Cihat Gündüz
November 8, 2014, 5:22 PM

I also still have this issue, and I'm even using 3.10.0 alpha nightly build from 08-11-2014.

Here's what my client is sending:
<presence to="2_bylvvdnobo0@1.1.1.1/10_msxoiknbtwc" from="10_msxoiknbtwc@1.1.1.1/de992e6b"><x xmlns="http://jabber.org/protocol/muc"/></presence>

And this is what Openfire is answering:
<presence xmlns="jabber:client" to="10_msxoiknbtwc@1.1.1.1/de992e6b" from="e1222-attendees@event.1.1.1.1/10_msxoiknbtwc" type="error"><x xmlns="http://jabber.org/protocol/muc"/><error code="404" type="cancel"><item-not-found xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></presence>

The setting is though are set as follows:

on List Room in Directory
on Make Room Persistent
off Make Room Moderated
off Make Room Members-only
on Can anyone discover real JIDs of occupants
on Allow Occupants to invite Others
on Allow Occupants to change Subject
off Only login with registered nickname
on Allow Occupants to change nicknames
on Allow Users to register with the room
on Log Room Conversations
Maximum Room Occupants: unlimited

So, this issue is clearly not yet solved for me.

Roman
November 10, 2014, 4:17 PM

Cihat Gündüz did you created the room over the MUC Service Plugin or over the Admin Console or over XMPP Client?

Cihat Gündüz
November 10, 2014, 6:30 PM

I create all rooms via XMPP Client.

What I did in the meantime was to downgrade Openfire to version 3.9.1 and this error disappeared. Another error appeared though that told me I had to configure the room as an "Instant Room". Maybe this issue appeared because I didn't configure the room. But if so, then the error I received with versions 3.9.2/3.9.3 didn't point me to configuring the room or that the room could be locked.

Assignee

Tom Evans

Reporter

Daryl Herzmann

Labels

Expected Effort

None

Ignite Forum URL

None

Components

Fix versions

Affects versions

Priority

Blocker
Configure