[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jabber-jdev
Subject:    RE: [JDEV] Groupchat with 1.2 problems continue
From:       David Waite <dwaite () jabber ! com>
Date:       2000-12-29 21:04:31
[Download RAW message or body]

You need to add a groupchat host entry, but to the service for the groupchat
transport, not to jsm.
All routing information is either within the jabber.xml or added on later
with server to server communication.

Also, normally people will run 'third party' or unstable loadable libraries
in another jabberd, and chain the two together - this way if there is a bug
in the library which corrupts memory or causes a segfault, it will only
affect that one component, not the entire jabber server. This is the
recommended setup for groupchat (although the conferencing component has
been pretty stable recently), and is at least decently documented in the
README.

-David Waite

-----Original Message-----
From: jdev-admin@jabber.org [mailto:jdev-admin@jabber.org]On Behalf Of Bruce
Nelson
Sent: Friday, December 29, 2000 2:39 PM
To: jdev@jabber.org
Subject: Re: [JDEV] Groupchat with 1.2 problems continue

P.S. -- Just to be clear on groupchat ... the difference is that you need to
use
an exec on a separate jabberd process -- using an additional
jabber_groupchat.xml file .. -- see below....

<jabberd> [this jabberd should be run from as an exec'd jabberd]
    <!--
        The parent jabberd should have this configured:
        <service id="groupchat_transport">
            <host>gc.go2.com</host>
            <exec>./jabberd/jabberd -c groupchat.xml</exec>
        </service>
    -->
  <service id="groupchat_transport">
    <host>gc.go2.com</host>
    <load><groupchat>./groupchat/groupchat.so</groupchat></load>
  </service>

  <service id="out">
    <host/>
    <stdout/>
  </service>

  <log id="groupchat_logs">
    <host/>
    <file>/u/oemmon/groupchat.log</file>
  </log>

 <xdb id="Outgoing_xdb">
    <host/>
    <stdout/>
  </xdb>

</jabberd>

"Malone, Pat" wrote:

> Ok,
> I tried renaming my service to groupchat.co.lsil.com (including the DNS
work
> - just an alias pointing to the same IP as jabber.co.lsil.com)
> and still have problems.  Here are the entrys in jabber.xml...
>    <agent jid="groupchat.co.lsil.com">
>           <name>Group Conferencing</name>
>           <description>You can create and participate in private
> chatrooms.</description>
>           <service>conferencing</service>
>           <groupchat/>
>           <register/>
>         </agent>
>
> <!-- Groupchat service -->
>   </service>
>    <service id="conference">
>    <load><groupchat>./groupchat.so</groupchat></load>
>   </service>
>
> This was returning with the message "Could not contact this agent. It is
> possible the agent is not operating"
> after a minute or two.  Debug logs seem to indicate jabber is trying to
talk
> with groupchat (including some nice "Dr. Pepper says" messaged in the
log!)
> with problems.
>
> For grins, I added "groupchat.co.lsil.com" as a 'host' entry.  This then
> returns an immediate server error 'not found'.
>     <host>jabber.co.lsil.com</host>
>     <host>groupchat.co.lsil.com</host>
>
> Looking around this morning, I found the jabberd_groupchat.xml file in the
> conferencing source tree that talks about a very different way to
integrate
> the groupchat than was explained in the 1.2 'how to' document.  Is this a
> better way to implement this?
> --
> <jabberd> [this jabberd should be run from as an exec'd jabberd]
>     <!--
>         The parent jabberd should have this configured:
>         <service id="groupchat_transport">
>             <host>groups.server.com</host>
>             <exec>jabberd -c this_file.xml</exec>
>         </service>
>     -->
>   <service id="groupchat_transport">
>     <host>groupchat.co.lsil.com</host>
>     <load><groupchat>groupchat.so</groupchat></load>
>   </service>
>
>   <service id="out">
>     <host/>
>     <stdout/>
>   </service>
>
>   <log id="groupchat_logs">
>     <host/>
>     <file>groupchat.log</file>
>   </log>
>
>   <xdb id="Outgoing_xdb">
>     <host/>
>     <stdout/>
>   </xdb>
> </jabberd>
> --
>
> Can someone with a working groupchat under 1.2 send me your jabber.xml?
> That might give me some clues.
>
> Thanks
>
> Pat
>
> _______________________________________________
> jdev mailing list
> jdev@jabber.org
> http://mailman.jabber.org/listinfo/jdev



[prev in list] [next in list] [prev in thread] [next in thread]