[JDEV] agent jids, service ids, and groupchat errors.

Otis Gospodnetic otis at neomeocorp.com
Thu Jan 4 17:38:35 CST 2001


Hello,

<snip>
Also, in jabber.xml I have two agents with the same 'jid'. User directory
and Groupchat are both jid='penguin.neomeo.com' which is a locally
resolvable host name.
Is this allowed? Do all jids have to be different even if they are on the
same Jabber server and do they have to correspond to resolvable host names?
</snip>

Nope, that isn't allowed--you DO need each agent to have a different, fully
resolvable DNS name.  So you might want to change the <agent id=""> for your
groupchat instance to something like groups.penguin.neomeo.com or anything
to make it different from your main jabberd host name.  You're getting "not
found" errors in your groupchat because the groupchat packets are being sent
to your main jabberd which doesn't know how to work them.  When you have a
separate id for your groupchat instance, those packets will be routed to the
jabberd that's forked specifically for group communication and things should
be working a lot better.


-- Thanks. I made the jids different. E.g. users.Neomeo.com and
chat.Neomeo.com although both are just aliases for penguin.Neomeo.com. Same
IP. I can telnet to all 3 of them to port 5222 and there is something
(jabberd) listening there.

Also, about your <service id=""> question:
<snip>
when you have <service id='XYZ'.... Does the XYZ have to correspond to
anything? (e.g. a host name, or a defined jid or...?)
</snip>

I'm not sure--on our jabber server, we've got <service
id="groupchat_transport"> but I don't know if that has to refer to anything
specific, and there's nothing else in our jabber.xml that refers to
groupchat_transport.  Anyone else able to clarify this?

-- I tried setting mine to that and setting it to 'conference', but neither
worked.

-- I'm using WinJab (the server is running on a Linux box) and pressing F7
lets me join a group.
I enter 'test' group, 'chat.Neomeo.com' for the server, 'otis' for my
username, and then all I get are Debug XML errors such as:

SENT: <iq type="get" id="wj_9" to="test at chat.neomeo.com"><query
xmlns="jabber:iq:groupchat"></query></iq>
SENT:
RECV: <iq type='error' id='wj_8' to='otis at penguin.neomeo.com/Work'
from='test at chat.neomeo.com'><query xmlns='jabber:iq:groupchat'/><error
code='502'>Remote Server Error</error></iq>

And on the server I get errors like:

20010104T23:27:08: [notice] (chat.neomeo.com): server connection timed out
20010104T23:27:08: [notice] (chat.neomeo.com): bouncing a packet to
test at chat.neomeo.com from otis at penguin.neomeo.com/Work: (null)
20010104T23:27:08: [notice] (chat.neomeo.com): bouncing a packet to
test at chat.neomeo.com from otis at penguin.neomeo.com/Work: (null)
20010104T23:27:08: [notice] (chat.neomeo.com): server connection timed out
20010104T23:27:08: [notice] (chat.neomeo.com): bouncing a packet to
test at chat.neomeo.com from otis at penguin.neomeo.com/Work: (null)
20010104T23:27:08: [notice] (chat.neomeo.com): bouncing a packet to
test at chat.neomeo.com from otis at penguin.neomeo.com/Work: (null)

This looks like a hostname issue now... but I _can_ nslookup and connect to
chat.Neomeo.com:5222 from the client machine.

Could this have anything to do with a firewall, even if both server and
client are on the same side of it (inside)?

I noticed that that I get errors when update.jabber.org is contacted....here
they are:

Server side:
20010104T23:24:06: [notice] (update.jabber.org): bouncing a packet to
959967039 at update.jabber.org/0.9.3.5 f
rom otis at penguin.neomeo.com/Work: (null)


Client side Debug XML:
RECV: <presence to='otis at penguin.neomeo.com/Work'
from='959967039 at update.jabber.org/0.9.3.5' type='error'><error
code='502'>Remote Server Error</error></presence>


Can anyone see what is going wrong here?

Thank you,

Otis
P.S.
I took out <agent jid="chat.Neomeo.com"..... from jabber.xml . I tried
following the instructions at
http://www.pipetree.com/jabber/groupchat-1.2.html and the sample jabber.xml
doesn't have that section.






More information about the JDev mailing list