[JDEV] jabber crash and socket timeout...
Lars.Nilsson4 at sas.no
Lars.Nilsson4 at sas.no
Thu May 2 02:37:18 CDT 2002
It must be some type of internal timeout:
Message log :
20020502T07:30:27: [notice] (sig.logserver): bouncing a packet to
sig.logserver from logClient1 at osli2076.net.sas.no/logClient02.05.02
09:30:00: Internal Timeout
Debug stdout is:
Thu May 2 09:30:27 2002 deliver.c:474 DELIVER 4:c2s <route
from='logClient1osli2076.net.sas.no/A163368' to='16 at c2s/A06B0D0'><message
to='logClient1osli2076.net.sas.no/logClient02.05.02 09:30:00'
from='sig.logserver' type='error'><body>5</body><error code='502'>Internal
Timeout</error></message></route>
-L-
-----------------------------------
Thomas Muldowney jdev at jabber.org <mailto:jdev%40jabber.org>
01 May 2002 11:48:57 -0500
Which timeout are you asking about? The TCP FIN state? The
<handshake/>? Or something else?
--temas
On Tue, 2002-04-30 at 08:34, Lars.Nilsson4 at sas.no
<mailto:Lars.Nilsson4 at sas.no> wrote:
> Hi.
>
> I just wondered if there is a setting for to lower the jabberd socket
> timeout for server side components.
> or a setting to just drop unsent messages.
>
> In a scenario where the server side component goes down and client
continue
> to send messages to the component; jabber will crash if the clients is
> sending to many messages.
> The reason why is that they will not be bounced before the timeout. And
when
> it occures there might be thousands of messages pending. This load makes
> jabber crash.
>
> If i either could just dropp messages on timeout or lower the socket
> timeout; that might solve the problem.
>
> regards
> Lars.
>
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org <mailto:jdev at jabber.org>
> <http://mailman.jabber.org/listinfo/jdev>
* Previous message: [JDEV] Adding MSN contacts <011607.html>
* Next message: [JDEV] server components <011614.html>
* Messages sorted by: [ date ] <date.html> [ thread ]
<thread.html> [ subject ] <subject.html> [ author ] <author.html>
More information about the JDev
mailing list