Skip to Content.
Sympa Menu

freetds - RE: [freetds] short read during bcp?

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] short read during bcp?
  • Date: Mon, 15 Dec 2003 19:55:24 -0500

> From: Lowden, James K
> Sent: December 15, 2003 5:03 PM
>
> This makes me think
> that we got a short read when we were looking for a DONE
> token, and instead
> of waiting for the server, we returned a zero length?

A bit of debugging code shows: No. We get ECONNRESET, but continue sending
packets:

pid: 5294:19:13:27.163315 dbconvert() called tds_convert returned 1
pid: 5294:Sending packet @ 19:13:27.163315
0000 07 01 01 67 00 00 01 00-74 00 72 00 00 00 09 00 |...g.... t.r.....|
[...]

pid: 5294:19:13:27.165266 tds_process_result_tokens() state is COMPLETED
pid: 5294:goodread: errno=54, "Connection reset by peer"
pid: 5294:19:13:27.171120 processing result tokens. marker is 0()
pid: 5294:19:13:27.171120 tds_process_default_tokens() marker is 0()
pid: 5294:19:13:27.172095 leaving tds_process_default_tokens() connection
dead
pid: 5294:Sending packet @ 19:13:27.172095
0000 07 01 01 0f 00 00 01 00-81 07 00 00 00 08 00 38 |........ .......8|
[...]

Not sure what to make of this. I know we're writing to a connection marked
TDS_DEAD; I'm not sure why. No error is returned from the server.

It might be my application, but if it is, I'd expect some error either from
the server or from FreeTDS. The messages I see are:

dbproc : 140048600
severity : 1
dberr : 20068
oserr : -1
dberrstr : Batch successfully bulk-copied to SQL Server.
oserrstr : OpenClient
dbproc : 140048600
severity : 9
dberr : 20006
oserr : 0
dberrstr : Write to SQL Server failed.
oserrstr : OpenClient
dbproc : 14005fd00
severity : 1
dberr : 20068
oserr : -1

Followed, eventually, by a segment fault do to using FD_SET on a
disconnected socket.

--jkl


-----------------------------------------
The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the original
message. Please note that we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page