Subject | Re: pumping very large records (30 megs!) |
---|---|
Author | spou |
Post date | 2003-08-18T15:10:49Z |
Ok then, that, once again, points to the network, and the bad guys
from netadmins domain.
I'll tell that to the boss, and let her fight this evil plot to
dominate the world. :-)
Spou
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
from netadmins domain.
I'll tell that to the boss, and let her fight this evil plot to
dominate the world. :-)
Spou
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
> At 12:27 PM 18/08/2003 +0000, you wrote:<helebor@t...>
> >--- In firebird-support@yahoogroups.com, Helen Borrie
> >wrote:what
> > > FB will (eventually) time out when it fails to get responses for
> >packet
> > > requests for a long enough time. When it gives up, the log will
> >show a
> > > (Client) type error, with an error code. So it's worth seeing
> > > Firebird messages were in the log before the TCP/IP messageshows
> >you?
> >I get this:
> >---------------------------------------------
> >server2 (server) sun aug 17 04:02:45 2003
> > INET/inet_error:read errno = 10054
> >
> >server2 (client) sun aug 17 04:02:46 2003
> > INET/inet_error: send errno = 10054
> >---------------------------------------------
> >
> >so apparently, the error starts at the server, but it would also
> >indicate the the source is the client. does it means anything to
>server
> No, because these aren't Firebird errors. The first one says the
> couldn't send a packet across the network and the network says(error
> 10054) "Connection reset by peer". That's a TCP/IP error - likewhat
> happens when your ISP cuts you off in the middle of a download(like mine
> does: if the statutory 4 hours are up - vaboom!) The second onejust says
> the packet it sent to the client didn't return a response - whichkinda
> follows on from the first one.
>
> heLen