Disco services become null after the upgrade to 3.7.0 Beta


I have some strange problem with Openfire 3.7.0 beta (it actually started with some nightly build after openfire_2010-07-28). I run windows version installed as a service, my clients are Miranda IM Jabber Unicode

After installing Openfire 3.7.0 beta almost all service names except for pubsub and proxy (as seen at "service discovery" Miranda window) get prepended with "null@" - e.g. "broadcast.server" becomes "null@broacast.server" etc. Two of these "null@" services are marked with a "red cross sign" and show "Info request error: Error 404: Not found" as node information. As a result i can't, for example, expand "broadcast" to see broadcast groups.

Except for the behaviour described above all services are actually functioning normally (broadcast messages are actually sent). I also get this at error.log (i use LDAP users and groups):

org.jivesoftware.openfire.group.GroupNotFoundException: Groupname null not found

LG comment:
<iq id="koRB4-2" to="igniterealtime.org" type="get">
<query xmlns="http://jabber.org/protocol/disco#items"/>

<iq id="koRB4-2" to="lg@igniterealtime.org/home" from="igniterealtime.org" type="result">
<query xmlns="http://jabber.org/protocol/disco#items">
<item jid="pubsub.igniterealtime.org" name="Publish-Subscribe service"/>
<item jid="null@clearspace.igniterealtime.org" name="Clearspace"/>
<item jid="null@conference.igniterealtime.org" name="Public Chatrooms"/>
<item jid="proxy.igniterealtime.org" name="Socks 5 Bytestreams Proxy"/>
<item jid="conference.igniterealtime.org" name="Public Chatrooms"/>
<item jid="null@search.igniterealtime.org" name="User Search"/>

this does not look good




Guus der Kinderen
January 12, 2011, 7:47 PM

This is caused by OF-399. Try a more recent nightly (anything after November 14th, 2010) and the problem should be gone.



Guus der Kinderen