[Spread-users] flooding problems?
Michael Rinner
rinner@student.uni-kl.de
Thu, 30 Aug 2001 09:09:26 +0200
This is a multi-part message in MIME format.
------=_NextPart_000_0016_01C13133.77764FA0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello,
I'm fairly new to Spread. I plan on using it for a distributed chat =
server system written in Java.
For evaluation I ran some performance tests and noticed that any =
listener will eventuallly stop working if a sender floods a connection =
continuously with messages that arrive faster than the listener may =
receive them. I first thought I had problems with my code but I managed =
to get the same results using modified versions of the User.java and =
Flooder.java classes. The receiver thread does not throw any exceptions, =
but just stops without ever recovering.
My question is, is there any way to prevent this flooding by letting a =
sender wait until messages have been received (I thought the =
poll()-method could be used for this, but it doesn't seem to work =
right?)
Or are there any known problems either with the Java-implementation or =
the Spread daemon on linux? I'm running on linux 2.40 with Sun JDK =
1.1.8.
I understand that this amount of traffic produced by the Flooder should =
not be expected in the chat environment I'm planning for. Still, I would =
like to react to those cases instead of hoping they will not happen...
Any help appreciated,
Michael Rinner
------=_NextPart_000_0016_01C13133.77764FA0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2526.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I'm fairly new to Spread. I plan on =
using it for a=20
distributed chat server system written in Java.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>For evaluation I ran some performance =
tests and=20
noticed that any listener will eventuallly stop working if a sender =
floods a=20
connection continuously with messages that arrive faster than the =
listener may=20
receive them. I first thought I had problems with my code but I managed =
to get=20
the same results using modified versions of the User.java and =
Flooder.java=20
classes. The receiver thread does not throw any exceptions, but just =
stops=20
without ever recovering.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My question is, is there any way to =
prevent this=20
flooding by letting a sender wait until messages have been received (I =
thought=20
the poll()-method could be used for this, but it doesn't seem to work=20
right?)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Or are there any known problems either =
with the=20
Java-implementation or the Spread daemon on linux? I'm running on linux =
2.40=20
with Sun JDK 1.1.8.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I understand that this amount of =
traffic produced=20
by the Flooder should not be expected in the chat environment I'm =
planning=20
for. Still, I would like to react to those cases instead of hoping they =
will not=20
happen...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Any help appreciated,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Michael =
Rinner</FONT></DIV></BODY></HTML>
------=_NextPart_000_0016_01C13133.77764FA0--