powered by Jive Software

Cannnot find other user in the same server...?

Hello everyone…

Need some help here…

I installed Openfire 3.3.3 on an Ubuntu 8.04 box…

The installation went smoothly without a glitch…

I could acces admin console and everything seems fine…

I connect to the server (localhost) via Netbeans Developer Collaboration plugins and could add user etc…

Other Netbeans user in my LAN could join and add user etc…

But strangely neither me or him could find each other…

Every time I try to add contact, I can’t find his name or user ID on user list, neither him…

I could connect to Netbeans >>> share.java.net:5222

What went wrong ?

Thank’s for replying…

regards,

Yuta

First you are using an outdated version of openfire. It is up to version 3.6. Second did you install the search plugin on the server? If you did it may not work anyway as your server version is too old.

Thanks for the reply Tood,

I already try to install the latest version 3.6…

But there was some sort of error which I forget what is precisely…

I remeber pasting to google and she spit an answer that there was a bug with this version…

Because Netbeans Collaboration Plugins need Openfire server later than 3.3.0, so I try to use 3.3.3…

And the search plugin was installed allright…

Any suggesstion ?

Many thanks

Update :

Try to use ver. 3.5.0…

Still the same error like ver. 3.6.0…

Netbeans spit this

“An unknown error occured when trying to initiate the collaboration session. Error : object does not represent a valid JID”

Strangely this error doesn’t show up on ver. 3.3.3…

Any thoughts ?

Many thanks

Well…

It seems like a dead end so far…

http://wiki.netbeans.org/CollabServer

Keep on digging…

http://collab.netbeans.org/servlets/ReadMsg?list=users&msgNo=162

Does anyone know how to manually edit the roster tables in openfire’s Mysql database in order to make people buddies and thus be able

to chat (since search doesn't work) ?

Thank's

We’re having exactly the same symtpoms with OpenFire 3.6.2-1 and NetBeans 6.5. I hope it will be fixed in the next version of one product or the other. But I’m not too confident because it seems unclear whether either has taken ownership of the issue.