[Spread-users] 1 problem with Spread.pm and 1 problem with spread daemon, was
george at omniti.com
Thu Jan 17 22:19:25 EST 2002
> 1) Spread.pm Perl module returns a Perl undef from multicast() in some
> circumstances. I've seen it when I call multicast() repeatedly without
> calling receive() in circumstances when there are incoming errors
> messages. It *might* be related to issue #2 below, however.
> 2) Somewhat more mysteriously, receive() only processes get
> spontaneously disconnected and receive() returns a CONNECTION_CLOSED
> correctly whenever a receiver is hammered continuously from more than 1
> process on the same box. The sending processes DO NOT get disconnected,
Each spread daemon maintains a separate queue for each client connected
to it. If the client's queue exceeds the max size, it (that specific
client) will be disconnected. You can lengthen the queue at compile
time, but you probably just need to make sure you process it faster.
> What would cause this? Is this a matter of not emptying the queue fast
> enough and buffers overflowing? If so, it would seem better to me to
> block on multicast() in the senders under this circumstance, subject to
> the connect() timeout value, of course.
> A debug ALL output from the Spread daemon itself can be found here:
> The offending event seems to be summarized by these lines (prefixed by
> line numbers):
> 344821:[Fri 18 Jan 2002 00:52:53] Sess_write: killing mbox 9 for not
> 347827:[Fri 18 Jan 2002 00:52:53] Sess_kill: killing session r0-9
> ( mailbox 9 )
> 347895:[Fri 18 Jan 2002 00:52:53] G_handle_kill: #r0-9#localhost is
> 347896:[Fri 18 Jan 2002 00:52:53] G_handle_kill in GOP
> -- Tom Mornini
> -- eWingz Systems, Inc.
> Spread-users mailing list
> Spread-users at lists.spread.org
More information about the Spread-users