RE: tcp/ip socket slowdown

Sounds like you are not closing the connection in your vb.net program
and the idle timeout is closing the connection on the iSeries side.
Then the data is processed.


Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rick DuVall
Sent: Thursday, May 04, 2006 3:37 PM
To: Midrange Systems Technical Discussion
Subject: RE: tcp/ip socket slowdown

Hi Walden,

        Thanks for your reply.  Unfortunately our power failed just
after I posted the question and the code is on a unit I can't reach just
now.  I will supply it as soon as possible.  I don't do much .net stuff,
I have someone else that is handling that and he tells me that he logs
the time once he has constructed the string that he is to send,  calls
whatever send api he is using (which I will provide later), and then
logs the time when it returns.
the elapsed is on the order of 3 mins depending on size which averages
about
1 - 2 meg and does not include the time spent building the string.  From
the server side, the server just sits there without using any cpu until
around the 3 min mark when it blooms up cpu usage and knocks out the
disassembly and saving of the data in about 3-4 secs.  I'll send the vb
code tomorrow.