Reply-To: "Patrick Grenier" From: "Patrick Grenier" To: References: Subject: Re: [PHP-DEV] PHP4 and Informix issues Date: Mon, 28 Aug 2000 21:52:31 +1300 Organization: Wcube Message-ID: <004701c010cd$4d42afd0$4a01a8c0@wcube.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal We had the same problem and we had to call a "guru" from Informix France. It does 3 months we still have only very few errors (I thought the problem was fixed but I've just talked to the client and he says that sometimes this problem appears. I need to verify that). Anyway, we have seen that when we stop/start Apache, the problem disappears most of the time. regards, Patrick Grenier. Systems developer Framfab France www.framfab.fr Messagerie : pgrenier@framfab.fr T. +33(0)1.55.48.11.00 - F. +33(0)1.47.35.00.00 ----- Original Message ----- From: Andrej Falout To: Ian Layton ; PHP Install List ; PHP General List ; PHP Dev List ; PHP DB List Cc: ; ; ; Sent: Sunday, August 27, 2000 3:07 AM Subject: RE: [PHP-DEV] PHP4 and Informix issues > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > ....another one > > Can you please look for bug #4468: "random ifx_pconnect code -439 > withifx_connect" and associated discussion in the list archives? > > Hey guys on CC line; anything new to say? This is obviously a > problem... > > Reminder for -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. > > Yours, Andrej Falout, http://www.falout.com ICQ 7628616 > #----------------------------------------------------------------- > globals "I_speak_for_myself.4gl" > > "I didn't know what I was doing. A blood vessel in my brain must > have burst" - Chief of police in Hesse, Germany, after he was > caught shoplifting ant poison worth a few dollars. > > > -----Original Message----- > > From: Ian Layton [mailto:ian.layton@home.com] > > Sent: Friday, 25 August 2000 5:25 > > To: PHP Install List; PHP General List; PHP Dev List; PHP DB List > > Subject: [PHP-DEV] PHP4 and Informix issues > > > > > > We are currently trying to use Informix Dynamic Server 2000 Version > 9.20.UC1 > > with PHP Version 4.0PR2. We are running into trouble with PHP's > connection > > to Informix. How we have it currently is using ifx_connect with > persistent > > connections turned off in the php.ini file with the line: > > > > ifx.allow_persistent = Off ; allow or prevent > > persistent link > > > > PHP apparently has a bug in the system where it does not look in the > php.ini > > files because PHP is still trying to use persistent connections on > the > > system. About 1/3 of the time we try to set up a database > connection, the > > following error occurs: > > > > Warning: ifx_pconnect : E [SQLSTATE=IX 000 SQLCODE=-439] in > ../sql.inc on > > line 28 > > Database server is currently processing SQL task. > > > > sql.inc line 28 reads as follows: > > > > if(! ($DBH = ifx_connect($InforData,$InforUser,$InforPass))) > > > > We are currently closing all db connection with ifx_close at the end > of > > every script. I have heard that ifx_connect is basically like > ifx_pconnect. > > Is that true even when persistent connections are turned off in the > ini > > file? Also, has anyone else come across this problem and a possible > > workaround for it? > > > > The site we are working on can expect upwards of a thousand database > hits > > per minute. Right now, this is not possible as a single debugger can > not be > > on the system without it bringing up the error. Any help anyone can > lend us > > on this would be greatly appreciated. > > > > Thank you > > Ian Layton > > Linuxhpc.com > > > > > > -- > > PHP Development Mailing List > > 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 > > > > > -----BEGIN PGP SIGNATURE----- > Version: PGPfreeware 6.0.2i > > iQA/AwUBOae/DBZH34ibpTRkEQIpiACfTbS3zR5AsWjjmbYRQ27TqSlriDgAoOMA > I5roIwSIw2hL/E+oIoQo+YU4 > =Ykbs > -----END PGP SIGNATURE----- > >