[JDEV] jserver stability problem
Lars Hansson
larshansson at yahoo.com
Tue Sep 19 10:23:22 CDT 2000
Ok, after a lot of testing and rebuilding it looks like it has something to
do with the transports. If I run jserver without any transports running
everything is just fine and dandy, even when I kill my client in a nasty
way. no core dumps in sight.
However, as soon as I start a transport both the transport and the jserver
will coredump if the client disconnects unexpectedly. The client doesnt even
have to subscribe to the transport in question, it is enough that any
transport is running and connected to the jserver in order for things to go
very bad.
I built the jserver and the libraries from the 1.0.1 dist and the other
transports from cvs.
The attached log includes snippets from jserver and icqtransport
Cheers
Lars Hansson
----- Original Message -----
From: Lars Hansson <larshansson at yahoo.com>
To: Thomas Muldowney <temas at box5.net>
Cc: <jdev at jabber.org>
Sent: Tuesday, September 19, 2000 02:13
Subject: Re: [JDEV] jserver stability problem
> Ok, here's the debug logfile (jserver.debug.log) and the jserver.xml file.
> I removed almost everything from the jserver.xml file and it still core
> dumped when I killed the client (JabberIM) without properly disconnecting
> (ie, I killed it from the taskmanager's process list).
>
> The box is a red hat 6.2 system and I compiled the jabber 1.0.1 source
> without any arguments to "configure" (ie, everything went to /usr/local)
>
> Cheers
> Lars
>
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: jabberlog.txt
URL: <https://www.jabber.org/jdev/attachments/20000919/b5081c65/attachment-0002.txt>
More information about the JDev
mailing list