Re: Informix returns SQLCODE=-439

>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. We do not use ifx_close call at the end of the PHP scripts (as it is not necessary according to PHP manual). Do you think it could have any influence to this problem? >BTW, is there a reason for not using persistent connections ? It should be a >lot faster. The reason is that the persistent connections didn't work on our platform (Solaris 2.6). Of course we started with persistent connections but immediately after the ifx_pconnect call the httpd proccess ended with core dump. As the non-persistent connections worked fine we didn't deeply tested that problem. I said that the problem has occured after a two month of troubleless run (with about 1000 visits a day). This would leads me to look for solving the problem in tuning the Informix server (adjustment of buffers, logs etc.) - the server seemed to slow down past few days. What do you think about it ? Thank you Mark