PHP :: Bug #21681 :: Isapi/mssql crashes under high load !!!!

Bug #21681	Isapi/mssql crashes under high load !!!!
Submitted:	2003-01-16 02:51 UTC	Modified:	2003-01-20 17:56 UTC
From:	frusti at frusti dot com	Assigned:
Status:	Closed	Package:	IIS related
PHP Version:	4.3.0	OS:	Windows 2000
Private report:	No	CVE-ID:	None

View Developer Edit

[2003-01-16 02:51 UTC] frusti at frusti dot com

I have a large PHP-Application that must run under Windows. ;-) 

Tested under Windows with PHP 4.3.0:
- IIS 5 with CGI 
- IIS 5 with ISAPI 
- Apache 2.0.43 with ISAPI

Problems
- witch CGI I have often problems with CGI-Error messages, but this problems are finished with ISAPI.
- System runs fine but sometimes every client becomes warnings the "Unable to connect to server" or "Unable to select database xxxx". 
Under IIS an restart of IIS does nothing wright, just a reboot helps.
Under Apache an restart of Apache release the problems.

!!! Please see also Bug #20330 http://bugs.php.net/bug.php?id=20330 - its the same Problem!!!!!!!

This can't be the solution?

Have everbody a answer to that problem or have same problems?

Thanks and best regards,
Frast Andreas

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports

[2003-01-16 03:00 UTC] frusti at frusti dot com

...

[2003-01-16 03:03 UTC] frusti at frusti dot com

sorry, have forgotten that just ISAPI is important!!!

[2003-01-17 20:53 UTC] sniper@php.net

Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip

[2003-01-18 14:29 UTC] frusti at frusti dot com

Sorry, I have also tested the latest snaps without any success!

Can it give problems with connection when the MSSQL-Server is configurated with Network-protocols Named Pipes and TCP/IP ??? Have someone experience with it?

Thanks and best regards,
Andi

[2003-01-18 18:38 UTC] fmk@php.net

This is a problem with missing thread safety in the Microsoft libraries used to build the MSSQL extension. It can be used with ISAPI but you can only get a stable system when using cgi or fastcgi.

The CGI error is not caused by either PHP or the MSSQL extension, but rather a problem with IIS. CGI processes are launched in forground, but the default setting for Windows NT/2000 is to optimize performence for background processes. If you switch this the CGI errors will go away.

[2003-01-18 18:48 UTC] frusti at frusti dot com

Hi,

thanks for your tip, I will test it and return a feedback.

[2003-01-19 19:02 UTC] mlaukast1 at hotmail dot com

A question for fmk@php.net:

Is there anything you can do for this problem? If it isn't a piece of code, perhaps a nice email to Microsoft or something like that...Please. Microsoft won't come to PHP guys asking if there's something they could do. It's you who must go to them. Furthermore, your email would be a lot more powerful than an email from some ordinary PHP developer. I mean, practically, this "bug" prevents me from using ISAPI at all and as you may have noted I'm not the only one. You've got to face the facts, because this "bug" might prevent ISAPI from ever becoming for production use. So please, do something about it. Hit the home run, because ISAPI is nearly there!

[2003-01-20 03:59 UTC] frusti at frusti dot com

A question for fmk@php.net:

can you give me please a tip to the CGI processes? Where must i set this? Is this on IIS oder direct on Windows 2000 to set? 
Or have you a more information about it? 

Thanks and best regards,
Andi

[2003-01-20 17:56 UTC] fmk@php.net

I have tried Microsoft sevral times but without luck. The DBLIB API we are using for the MSSQL extensions has not been updated since SQL Server 6.0, though Microsoft has released at least 3 versions since then.

My best hope right now is to use FreeTDS on Win32 (as it is done on *nix) but the Win32 port is, to my best knowledge, not stable at this point. As soon as I have a FreeTDS version of DBLIB I'll make the MSSQL extension work with it.

[2003-01-21 05:46 UTC] dipsy_9001 at yahoo dot fr

I already had random "CGI Error" (HTTP 502 error) with IIS5+W2K+CGI under heavy load.
I solved the pb by turning on the "Allow interaction with desktop" option for IIS Admin service.
I guess there was sthg that needed to access desktop in my CGI initialization phase (in some external libs?). Maybe it is the same case with php.exe
I don't know if it can tamper with web server security.

[2003-01-28 05:19 UTC] mlaukast1 at hotmail dot com

Thanks for the tip dipsy_9001@yahoo.fr! It helped me a lot. It considerably reduced the appearance of the 502 CGI Error.

	php.net \| support \| documentation \| report a bug \| advanced search \| search howto \| statistics \| random bug \| login
go to bug id or search bugs for


Copyright © 2001-2025 The PHP Group All rights reserved.	Last updated: Mon Jul 14 21:01:33 2025 UTC