Hate to bring this up...
When I restart the transport, it forks like 20 processes and eats up a
very significant chunk of memory (I'm on a VPS, so memory is pricey).
It grinds for a minute and then the usage drops to something sane.
Although after a while memory consumption rises again and something
inside the transport locks up, because it doesn't even respond to
SIGTERM, i have to SIGKILL it every time. And my server (ejabberd)
complains about that too
<<<
(10:34:45 AM) jabber.exceede.com: ([EMAIL PROTECTED]) The process
<0.15193.2> is consuming too much memory: [{heap_block_size,1682835},
{mbuf_size,0},{stack_size,26},{heap_size,1352042}].
Process type: s2s_out
Serviced domain: icq.jabber.exceede.com
Possible reason: the process is blocked trying to send data over its
TCP connection.
Command to kill this process: kill [EMAIL PROTECTED] <0.15193.2>
(10:38:59 AM) jabber.exceede.com: ([EMAIL PROTECTED]) The process
<0.15193.2> is consuming too much memory: [{heap_block_size,1346269},
{mbuf_size,0},{stack_size,65},{heap_size,819819}].
Process type: s2s_out
Serviced domain: icq.jabber.exceede.com
Possible reason: the process can't process messages faster than they
arrive. Current function is xml:'-crypt/1-lc$^0/1-0-'/1
Command to kill this process: kill [EMAIL PROTECTED] <0.15193.2>
>>>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"py-transports" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/py-transports?hl=en
-~----------~----~----~----~------~----~------~--~---
