Up Prev Next
From: michael dot x dot peppler at jpmchase dot com
Subject: Re: ct_con_alloc failed / Apache / FastCGI / DBD::Sybase
Date: Feb 15 2008 9:56AM
I think this list is a reasonable place to ask this question :-)
The error indicates that the Sybase OpenClient code can't allocate a new
connection handle. This can be due to memory issues, but more likely there
is some issue in the fastcgi setup where the Sybase OpenClient code gets
Which version of DBD::Sybase are you using?
Sent by: email@example.com
Please respond to
ct_con_alloc failed / Apache / FastCGI / DBD::Sybase
I don't really know if this is the right list I should write
to but in doubt...
I've got a webserver (apache) running a database search web
interface through fastcgi.
Unfortunately, when I try to connect to Sybase with my
application (that fastcgi try to handle) it fails with this
error message in error_log of apache :
stderr: ct_con_alloc failed at
In this case, it is Apache that handle the request to DB
If I make fastcgi listening a socket written by my perl
script, everything is ok.
I set up a lot of different Env in my apache config file but
it looks like it is not enough such as :
SetEnv SYBROOT /Applications/Sybase/System
SetEnv SYBASE /Applications/Sybase/System
SetEnv SCROOT /Applications/Sybase/System/sybcent41
SetEnv SYBASE_OCS OCS-12_5
SetEnv SYBASE_SYSAM SYSAM-1_0
SetEnv SYBASE_JRE /Applications/Sybase/Sysytem
SetEnv SYBASE_ASE ASE-12_5
SetEnv LIB /Applications/Sybase/System/OCS-12_5/lib
SetEnv LC_ALL C
SetEnv LANG C
So I wondered if someone has already faced such problem and
could give me a clue?
Thanks a lot.
Sorry for disturbing the list.
Biological Software and Databases Group
+33 1 44 38 95 98
tuco at_ pasteur dot fr
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.