Re: PHP and Informix
Posted in 2004
This is a multipart message in MIME format. --=_alternative 0056130B86256EEF_= Content-Type: text/plain; charset="US-ASCII" Fernando, I believe we have tried both pconnect and connect. One of the two seems to be a bit better at preventing the error, but doesn't eliminate this as an issue. I think we may have the most up-to-date csdk on the linux box. We have checked in the php lists to find that not too many people have this problem, so there really isn't a known fix yet that I'm aware of. Thanks for being willing to help us though! C Geier System Admin/IS support St. Paul, MN Fernando Nunes <spam@domus.online.pt> Sent by: owner-informix-list@iiug.org 08/13/2004 08:25 AM Please respond to Fernando Nunes <spam@domus.online.pt> To informix-list@iiug.org cc Subject Re: PHP and Informix CKGeier@nwc.edu wrote: > This is a multipart message in MIME format. > --=_alternative 005CDBF086256EEE_= > Content-Type: text/plain; charset="US-ASCII" > > We occasionally have issues with Php and Informix. If we have a lot of > activity, after a few hours users start getting -439 errors. Php runs on > RedHat Linux 8 and we use an Apache webserver. The problem only exists, so > I'm told, when RedHat is mixed with Apache. We have called Informix on > this and have tried a few things, but not every suggestion has been tried > yet. The 'fix' is to restart Apache when the errors start happening; if we > don't do this eventually the web pages are completely unusable by everyone > who tries to use them. > Are you using permanent connections (pconnect instead of connect)? It looks like you are send SQL instrunctions through a connection which is in use by another page. This looks like a problem in the php-informix layer. Did you check in the PHP mailing lists? Eventually try a newer version of IBM Informix CSDK. Regards. --=_alternative 0056130B86256EEF_= Content-Type: text/html; charset="US-ASCII" <br><font size=2 face="sans-serif">Fernando,</font> <br> <br><font size=2 face="sans-serif">I believe we have tried both pconnect and connect. One of the two seems to be a bit better at preventing the error, but doesn't eliminate this as an issue. I think we may have the most up-to-date csdk on the linux box. We have checked in the php lists to find that not too many people have this problem, so there really isn't a known fix yet that I'm aware of. </font> <br> <br><font size=2 face="sans-serif">Thanks for being willing to help us though! </font> <br><font size=2 face="sans-serif"><br> C Geier<br> System Admin/IS support<br> St. Paul, MN<br> </font> <br> <br> <br> <table width=100%> <tr valign=top> <td width=40%><font size=1 face="sans-serif"><b>Fernando Nunes <spam@domus.online.pt></b> </font> <br><font size=1 face="sans-serif">Sent by: owner-informix-list@iiug.org</font> <p><font size=1 face="sans-serif">08/13/2004 08:25 AM</font> <table border> <tr valign=top> <td bgcolor=white> <div align=center><font size=1 face="sans-serif">Please respond to<br> Fernando Nunes <spam@domus.online.pt></font></div></table> <br> <td width=59%> <table width=100%> <tr> <td> <div align=right><font size=1 face="sans-serif">To</font></div> <td valign=top><font size=1 face="sans-serif">informix-list@iiug.org</font> <tr> <td> <div align=right><font size=1 face="sans-serif">cc</font></div> <td valign=top> <tr> <td> <div align=right><font size=1 face="sans-serif">Subject</font></div> <td valign=top><font size=1 face="sans-serif">Re: PHP and Informix</font></table> <br> <table> <tr valign=top> <td> <td></table> <br></table> <br> <br> <br><font size=2><tt>CKGeier@nwc.edu wrote:<br> <br> > This is a multipart message in MIME format.<br> > --=_alternative 005CDBF086256EEE_=<br> > Content-Type: text/plain; charset="US-ASCII"<br> > <br> > We occasionally have issues with Php and Informix. If we have a lot of <br> > activity, after a few hours users start getting -439 errors. Php runs on <br> > RedHat Linux 8 and we use an Apache webserver. The problem only exists, so <br> > I'm told, when RedHat is mixed with Apache. We have called Informix on <br> > this and have tried a few things, but not every suggestion has been tried <br> > yet. The 'fix' is to restart Apache when the errors start happening; if we <br> > don't do this eventually the web pages are completely unusable by everyone <br> > who tries to use them.<br> > <br> <br> Are you using permanent connections (pconnect instead of connect)?<br> It looks like you are send SQL instrunctions through a connection which <br> is in use by another page.<br> <br> This looks like a problem in the php-informix layer. Did you check in <br> the PHP mailing lists?<br> <br> Eventually try a newer version of IBM Informix CSDK.<br> <br> Regards.<br> </tt></font> <br> --=_alternative 0056130B86256EEF_=-- sending to informix-list