<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Wouldn't it make sense if you had a Hobbit client running on the
same server as the Hobbit server?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>=G=<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Gary Baluha
[mailto:gumby3203@gmail.com] <br>
<b>Sent:</b> Tuesday, January 29, 2008 10:36 AM<br>
<b>To:</b> hobbit@hswn.dk<br>
<b>Subject:</b> Re: [hobbit] Large number of TIME_WAITs<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Red Hat ES 4 Update 5.<br>
That's what I normally would think, but it doesn't make any sense that the
source AND destination are both localhost or the local IP. It's as though
the Hobbit server is trying to communicate with itself using network
sockets. It would make more sense if either the source or destination was
a client IP, but that isn't the case.<o:p></o:p></p>
<div>
<p class=MsoNormal>On Jan 29, 2008 10:15 AM, Hubbard, Greg L <<a
href="mailto:greg.hubbard@eds.com">greg.hubbard@eds.com</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>What OS? Some operating systems allow network connections to
hang around a bit after disconnection. On Solaris you can set a parameter
to reduce the timeout period. Hobbit could trigger this because each
client connects to the server, sends a data blast, and then disconnects.</span><o:p></o:p></p>
<blockquote style='margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> Gary Baluha [mailto:<a
href="mailto:gumby3203@gmail.com" target="_blank">gumby3203@gmail.com</a>] <br>
<b>Sent:</b> Tuesday, January 29, 2008 8:58 AM<br>
<b>To:</b> <a href="mailto:hobbit@hswn.dk" target="_blank">hobbit@hswn.dk</a><br>
<b>Subject:</b> [hobbit] Large number of TIME_WAITs</span><o:p></o:p></p>
<div>
<div>
<p class=MsoNormal>I noticed something strange on my Hobbit server, though I'm
not sure if it's a problem or not. There are about 140 TIME_WAITs from
the local IP of the Hobbit server, and about 30 TIME_WAITs from localhost, all
using port 1984. They look something like this:<br>
<br>
0 0 <a href="http://1.2.3.4:42389" target="_blank">1.2.3.4:42389</a>
<a href="http://1.2.3.4:1984" target="_blank">1.2.3.4:1984</a>
TIME_WAIT<br>
0 0 <a href="http://1.2.3.4:42394" target="_blank">1.2.3.4:42394</a>
<a href="http://1.2.3.4:1984" target="_blank">1.2.3.4:1984</a>
TIME_WAIT<br>
0 0 <a href="http://1.2.3.4:42399" target="_blank">1.2.3.4:42399</a>
<a href="http://1.2.3.4:1984" target="_blank">1.2.3.4:1984</a>
TIME_WAIT<br>
0 0 <a href="http://1.2.3.4:42396" target="_blank">1.2.3.4:42396</a>
<a href="http://1.2.3.4:1984" target="_blank">1.2.3.4:1984</a>
TIME_WAIT<br>
0 0 <a href="http://1.2.3.4:42397" target="_blank">1.2.3.4:42397</a>
<a href="http://1.2.3.4:1984" target="_blank">1.2.3.4:1984</a>
TIME_WAIT<br>
<br>
0 0 <a href="http://127.0.0.1:42310"
target="_blank">127.0.0.1:42310</a>
<a href="http://127.0.0.1:1984" target="_blank">127.0.0.1:1984</a>
TIME_WAIT<br>
0 0 <a href="http://127.0.0.1:42309"
target="_blank">127.0.0.1:42309</a>
<a href="http://127.0.0.1:1984" target="_blank">127.0.0.1:1984</a>
TIME_WAIT<br>
0 0 <a href="http://127.0.0.1:42315"
target="_blank">127.0.0.1:42315</a>
<a href="http://127.0.0.1:1984" target="_blank">127.0.0.1:1984</a>
TIME_WAIT<br>
0 0 <a href="http://127.0.0.1:42322"
target="_blank">127.0.0.1:42322</a>
<a href="http://127.0.0.1:1984" target="_blank">127.0.0.1:1984</a>
TIME_WAIT<br>
0 0 <a href="http://127.0.0.1:42320"
target="_blank">127.0.0.1:42320</a>
<a href="http://127.0.0.1:1984" target="_blank">127.0.0.1:1984</a>
TIME_WAIT<br>
<br>
There are also a few on various other ports:<br>
0 0 <a href="http://127.0.0.1:42246"
target="_blank">127.0.0.1:42246</a>
<a href="http://127.0.0.1:29021" target="_blank">127.0.0.1:29021</a>
TIME_WAIT<br>
0 0 <a href="http://127.0.0.1:42301"
target="_blank">127.0.0.1:42301</a>
<a href="http://127.0.0.1:29023" target="_blank">127.0.0.1:29023</a>
TIME_WAIT<br>
0 0 <a href="http://127.0.0.1:42362"
target="_blank">127.0.0.1:42362</a>
<a href="http://127.0.0.1:29017" target="_blank">127.0.0.1:29017</a>
TIME_WAIT<br>
0 0 <a href="http://127.0.0.1:29030"
target="_blank">127.0.0.1:29030</a>
<a href="http://127.0.0.1:42380" target="_blank">127.0.0.1:42380</a>
TIME_WAIT<br>
0 0 <a href="http://127.0.0.1:42348"
target="_blank">127.0.0.1:42348</a>
<a href="http://127.0.0.1:29019" target="_blank">127.0.0.1:29019</a>
TIME_WAIT<br>
<br>
<br>
Any idea why there should be so many of them, particularly on the localhost address?
And any idea if this looks abnormal or not?<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>