[JDEV] Something up with jabber.org?

[Andy Ames]

Hi,

I had the same problem the other day with jabber.org.

See "[JDEV] Receiving others' messages"

Andy

-----Original Message-----
From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
Matthias Wimmer
Sent: Thursday, August 07, 2003 1:28 AM
To: jdev at jabber.org
Subject: Re: [JDEV] Something up with jabber.org?


Hi Mikael, hi Peter!

Mikael Hallendal schrieb am 2003-07-29 17:47:32:
> I got some reports from people having problems connecting to jabber.org
> with Gossip and when trying it out I got this:
> 
> Sent:
> <iq id="msg_4" type="get">  
>   <query xmlns="jabber:iq:auth"> 
>     <username>hallski</username>
>   </query>
> </iq>
> 
> Recv:
> 
> <iq type='error' id='keh_1331'>
>   <query xmlns='jabber:iq:auth'>
>     <username>XXXXX XXXXXX</username>
>   </query>
>   <error code='406'>Not Acceptable</error>
> </iq>
> 
> Where the XXX part is a name I've never seen before.

I don't know if it is the same problem, but I am aware of a similar
problem on my own jabber server (amessage).

On amessage it happens from time to time, that messages are delivered to
wrong users. This is caused if the client connection manager crashes
(and gets restarted) while the session manager continued to run.

The problem with this is that the individual TCP/IP connections the
client connection manager handles are addressed as <filedescriptor>@c2s.
If the client connection manager crashes the session manager is not
informed, that all the clients went offline and keeps their state as
"online" and their connection as it was.
If new clients come online they get the same filedescriptors again
(filedescriptors are handles that are just incremented) and if users,
that were online before get messages they are directed to their old file
descriptors and the wrong user gets the message.
Even worse: The the new user sends a message, he is identified by his
file descriptor by the session manager that looks up the corresponding
JID of the user and finds the old one. Therefore the new user sends is
messages with the JID of the old user.

I wrote a fix for this, but have not yet applied it to my own server, as
I do not have much time at the moment.

I could imagine that something similar happens in your case ... maybe
the sessionmanager thinks you are already authenticated as someone else
and does not accept that you try to authenticate as "hallski". Just a
guess, never noticed this problem on my own Jabber server.


Tot kijk
    Matthias