[Fwd: Re: [Spread-users] Spread 'kill' my server]
caudy at jhu.edu
Thu Feb 6 08:40:25 EST 2003
As usual, I forgot to reply to all. Sorry.
-------- Original Message --------
Subject: Re: [Spread-users] Spread 'kill' my server
Date: Thu, 06 Feb 2003 08:39:44 -0500
From: Ryan Caudy <caudy at jhu.edu>
To: Cosimo Calabrese <the_tube at libero.it>
References: <H9VWF1$878EB1FFF13DCC22709871B96D139D32 at libero.it>
Cosimo Calabrese wrote:
>I'm working with a group communication Java application based on Spread; this application sends messages to Spread, and Spread sends them in multicast to a cluster.
>When I try to send a lot of messages per second, Spread kills the receiving group member after the reception of a certain number of messages. The java application reports this error:
>spread.SpreadException: read(): java.net.SocketException: Connection reset
>This error doesn't happen when I send messages at a slower rate.
>Any hint? I think that Spread kills me when the input buffers are full. How can I resolve this problem? Should I modify any of the #define variables?
>Spread-users mailing list
>Spread-users at lists.spread.org
Yes, Spread does disconnect client sessions for not receiving when its
buffers get full. To solve this, you could look at extending buffers to
make it more unlikely that Spread will need to disconnect your client.
However, if its really a case of your sender overwhelming the receiver,
the only solution that will prevent this problem from recurring is
implementing some flow control. Probably something simple is all you
will need. What is you application like? What is your Spread
configuration like? Someone can try to answer your question more
specifically with further information.
More information about the Spread-users