Actually I switched from jabberd2 to ejabberd over the weekend and
noticed this behavior as well. I don't know what's going on, but I can
certainly tell that it was not happening before the switch and is
happening now.
I haven't timed it, but it seems to take around half a minute to a
minute for the transport to show as online on my roster, and another
fifteen seconds or so for AIM contacts to show up. In all it may take
around a minute to a minute and a half for AIM contacts to show up after
the jabber connection is working. These times are all estimates.
~Chris
Alexey Nezhdanov wrote:
> ? ????????? ?? ??????? 24 ?????? 2006 21:09 Daniel Henninger ???????(a):
>
>> =( Maybe, but I hate that there's nothing concrete I can really tell
>> you there. I wonder why gaim is behaving better... What jabber
>> server are you running/connecting through?
>>
> ejabberd in one case (where it was slower)
> jabberd13 in other (where it was faster)
>
> I think I'd say "forgot it, I'll do more testing and then report back" now.
> The problem is really too not specific and leaves us only to guess why it is
> happened.
>
> There can be another answer: may be AOL had been doing something nasty...
>
From [EMAIL PROTECTED] Wed Jan 25 09:30:26 2006
From: [EMAIL PROTECTED] (Conrad Burger)
Date: Wed Jan 25 09:30:43 2006
Subject: [py-transports] pymsnt multiple problems
Message-ID: <[EMAIL PROTECTED]>
Hi
We are currently experiencing multiple problems with pymsnt.
We have pymsnt 0.10.2 setup on FreeBSD 5.4 connecting to an ejabberd 0.9.8
cluster.
The gateway works well until about 1000 users log on to it. It then starts to
log errors until it comes to a halt. We then have to kill -9 the process and
start it up again.
The errors:
-----------------------------------------------------------------------
Traceback (most recent call last):
--- <exception caught here> ---
File "/usr/local/lib/python2.4/site-packages/twisted/internet/default.py",
line 490, in doSelect
[], timeout)
exceptions.ValueError: filedescriptor out of range in select()
Traceback (most recent call last):
--- <exception caught here> ---
File "/usr/local/lib/python2.4/site-packages/twisted/internet/base.py", line
423, in runUntilCurrent
call.func(*call.args, **call.kw)
File "/usr/local/lib/jabber/pymsn/legacy/msnw.py", line 32, in initMe
MSNConnection.removeMe(self)
File "/usr/local/lib/jabber/pymsn/legacy/msnw.py", line 52, in removeMe
LogEvent(INFO, self.session.jabberID)
exceptions.AttributeError: 'NoneType' object has no attribute 'jabberID'
'removeMe called more than once!'
Traceback (most recent call last):
--- <exception caught here> ---
File "/usr/local/lib/python2.4/site-packages/twisted/internet/tcp.py", line
98, in doRead
return Connection.doRead(self)
File "/usr/local/lib/python2.4/site-packages/twisted/internet/tcp.py", line
252, in doRead
raise
File "/usr/local/lib/python2.4/site-packages/twisted/internet/tcp.py", line
239, in doRead
data = self.socket.recv(self.bufferSize)
OpenSSL.SSL.SysCallError: (60, 'Operation timed out')
Traceback (most recent call last):
-----------------------------------------------------------------------
Does anyone know why we get these errors?
How many connections from a single IP does Microsoft allow to connect to their
passport service?
Any help would be appreciated.
Cheers
Conrad Burger
