[JDEV] roster out of sync w/ reality
mass at akuma.org
Thu Feb 7 19:05:11 CST 2002
I believe this is a TCP issue when there is no concept of keepalive
going. The socket does not verify the remote connection is still up, and
will happily sit there as long as there is no traffic present.
Also, there is a retry period of (I believe) a maximum of 11 minutes
before the socket is identified as failed. Sometimes the network can be
broken and reestablished minutes later, but the socket hasn't been broken.
Peter Saint-Andre wrote:
>I'm not sure which client multiplexer we're using right now on jabber.org
>but I know that I've seen this problem with jpolld. It seems to actually
>be a problem with freeing up file descriptors at the OS level but I don't
>know enough to say more than that. :)
>email+jabber: stpeter at jabber.org
>On Wed, 6 Feb 2002, Pat Mahoney wrote:
>>(please cc: me, not subscribed)
>>(using gabber 0.8.5 and jabber.org)
>>Numerous times my roster claims a contact is available when in fact he
>>is not. It seems to happen when he (a dialup user) kills pppd without
>>explicitly logging out of jabber. He can remain in this state of limbo
>>indefinitely (I've witnessed a 6 hour stretch). It seems that he only
>>remains in limbo as long as no one attempts to contact him in any way
>>(either chatting or trying to extract client info, etc).
>>Even after someone (me) tries to chat with him while he is in limbo, it
>>takes a few (5, 10? I'm not really sure, and it varies) minutes for
>>the roster to report him as offline.
>>I'm sorry I don't have a good reproducible case. I consider this a bug
>>though, as it is extremely annoying. For what it's worth, I never saw
>>this back when I used AIM, though I don't believe I ever had a buddy
>>who had no other buddies aside from me (as is the case with this
>>particluar jabber user).
>>Pat Mahoney <patmahoney at gmx.net>
>jdev mailing list
>jdev at jabber.org
More information about the JDev