FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Kass, Sharon [mailto:Sharon.Kass AT gs.com]
> Sent: December 1, 2003 2:39 PM
> 
> Does anybody know what would cause a connection to be dropped (or a
> secondary connection to be established)? And is there some 
> way for me to
> specify a username/password to be used if FreeTDS does try to 
> re-connect?

Sharon, 

Here's the odd bit of your trace:

> 1   -> prepare for DBD::Sybase::db (DBI::db=HASH(0x164c68)~INNER '
>                 INSERT into gs_location
>                         VALUES ('1001041LO','ME1 E1011','RC   
>      ','ME1
> ','Outlets',0,0,'',user_name(),getdate())
>         ' undef)
>     syb_st_prepare() parent has active kids - opening new connection
                       ^^^^^^^^^^^^^^^^^^^^^^

A message like that makes me suspect that FreeTDS is misinterpreting the
data stream, possibly because the server sent us something we didn't expect.
If you're not using a recent snapshot (something that includes Bill
Thompson's ct-lib upgrade, check ChangeLog), it's time to upgrade.  Even if
that doesn't solve the problem, it'll be the best place to begin.  

Based on the message, it seems DBD::Sybase is opening a new connection,
which it will do if need be, cf. "perldoc DBD::Sybase".  But normally that's
transparent.  There's no reason it should forget the user credentials.  

It may also be that the ct-lib layer is somehow confused.  I think that's
less likely, but it's why we should be working with Bill's new code. 

To troubleshoot this further, we'd need to see the relevant section (or all)
of the TDSDUMP log.  I'd be particularly interested in what happened
immediately prior to and just after the above insert statement.  You may
need to trim/compress the log if you post it here; the limit is 75 KB.  

Regards, 

--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.