From: "Danny Heijl" <danny.heijl@pandora.be>
To: "\"Marek Novicky\"" <novicky@aarongroup.cz>
Cc: "PHP-Development" <php-dev@lists.php.net>
Subject: Re: [PHP-DEV] Informix returns SQLCODE=-439
Date: Tue, 7 Mar 2000 08:15:02 +1300
Message-ID: <001501bf87a0$4678c420$a59382c3@eunet.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal

-439 : Database server is currently processing an SQL task.

"You attempted to call an SQL routine or attempted to execute an SQL
statement within a signal handling function/routine or a callback
function/procedure. Use only the sqldone() and sqlbreak() library functions
inside your INFORMIX-ESQL/C callback function. Use only the ECO-SQD and
ECO-SQB library routines inside your ESQL/COBOL callback procedure. In
addition, if you want to unregister your callback function in
INFORMIX-ESQL/C, you can invoke the sqlbreakcallback() callback registration
function within your callback procedure. If you want to unregister your
callback procedure in ESQL/COBOL, you can invoke the ECO-SQBCB callback
registration routine within your callback procedure."


This seems to suggest that a signal handling routine tries to execute an
ESQL/C statement while another statement is still active.

There are no signal handling routines or ESQL/C callback functions inside
the PHP/Informix driver, it is all strictly synchronous, so I see no obvious
cause for your problem. Unless perhaps the user hits the stop button on his
browser, Apache fires the corresponding signal to modphp aborting the
request, with the  Informix code still hanging in the connect code, and a
new request is processed with the connect code still not finished. I don't
know if such a scenario is possible, I am just guessing here.

I don't know if something similar could happen if a request hits the time
limit.
I certainly never experienced the problem, and it has not been reported
before.

BTW, is there a reason for not using persistent connections ? It should be a
lot faster.


Danny
---



-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net
For additional commands, e-mail: php-dev-help@lists.php.net
To contact the list administrators, e-mail: php-list-admin@lists.php.net

