Apache::DBI with Sybase - What's wrong?

["Graf, Chris" <cg...@uo.com>]

It seems that once processes start getting reused, I wind up with a ton of
DB error messages in my error_log. 

They seem to start like this:

ct_cmd_alloc failed at
/usr/local/lib/perl5/site_perl/5.005/sun4-solaris/DBD/Sybase.pm line 159.
DBD::Sybase::db ping failed: OpenClient message: LAYER = (5) ORIGIN = (3)
SEVERITY = (5) NUMBER = (6)
Message String: ct_cancel(): network packet layer: internal net library
error: Net-Library operation terminated due to disconnect

Then a whole host of these start popping up:

DBD::Sybase::db ping failed: OpenClient message: LAYER = (1) ORIGIN = (1)
SEVERITY = (1) NUMBER = (60)
Message String: ct_cancel(CONN,ALL): user api layer: external error: There
is a usage error.  This routine has been called at an illegal time.

OpenClient message: LAYER = (1) ORIGIN = (1) SEVERITY = (1) NUMBER = (60)
Message String: ct_close(FORCE): user api layer: external error: There is a
usage error.  This routine has been called at an illegal time.



What is happening on the user end at this time - 500s? Any insight would be
incredibly helpful at this point.


Thanks

Chris

Re: Apache::DBI with Sybase - What's wrong?

[Michael Peppler <mp...@peppler.org>]

Graf, Chris writes:
 > 
 > It seems that once processes start getting reused, I wind up with a ton of
 > DB error messages in my error_log. 
 > 
 > They seem to start like this:
 > 
 > ct_cmd_alloc failed at
 > /usr/local/lib/perl5/site_perl/5.005/sun4-solaris/DBD/Sybase.pm line 159.
 > DBD::Sybase::db ping failed: OpenClient message: LAYER = (5) ORIGIN = (3)
 > SEVERITY = (5) NUMBER = (6)
 > Message String: ct_cancel(): network packet layer: internal net library
 > error: Net-Library operation terminated due to disconnect

I'm not familiar with Apache::DBI, so I don't know exactly in what
situation it calls ping()... In this case it looks like ping fails (ie 
the connection to the server has been killed) but the sequence of
calls that follow is incorrect.

 > What is happening on the user end at this time - 500s? Any insight would be
 > incredibly helpful at this point.

I think there's a good chance of 500s, but maybe not. It's possible
that these are internal warnings, and that the initial failed ping()
causes a database reconnect and that things continue cleanly...

Michael
-- 
Michael Peppler         -||-  Data Migrations Inc.
mpeppler@peppler.org    -||-  http://www.mbay.net/~mpeppler
Int. Sybase User Group  -||-  http://www.isug.com
Sybase on Linux mailing list: ase-linux-list@isug.com