Jump to content

dylanrolfey

New Members
  • Posts

    6
  • Joined

  • Last visited

    Never

Everything posted by dylanrolfey

  1. OK so just to let everyone know the FastCGI module worked great. Same test, no errors! Hooray. Pretty simple to install once you get your head around it. I just followed this and it worked great. http://learn.iis.net/page.aspx/247/using-fastcgi-to-host-php-applications-on-iis-60/ Dylan
  2. yeah mate really not sure, i am not that experienced as a sys admin to do any of these things, i just stab around in the dark till it works lol. i will let you know how i go, we are setting it up this weekend, i will let you know of the results
  3. hey mate, found another bug report similar to the one above. http://bugs.php.net/bug.php?id=19541&edit=3 it says at the bottom Maybe using FastCGI is the answer. I am going to try it out and let you know, but I only have a production environment at the moment and no testing ground so it might take me a while... let me know if it is of any help http://phplens.com/phpeverywhere/fastcgi-php
  4. found this article, its a bit old so should have resolved by now, but maybe helpful. they suggest to loop the connect script until it connects :-\ http://bugs.php.net/bug.php?id=29074 hope it helps. i am going to try it out tomorrow at work.
  5. No, as such still am having problems. And now I have fears that if my website does get some serious traffic, my setup will not be able to handle it. I don't know if this is common or not ??? but it sucks lol
  6. Hi everyone, I keep getting this error coming up: PHP Warning: mssql_connect() Unable to connect to server: localhost,2168 However it seems that it is only coming up when there is a heavy load on the server. To explain, I have setup a PHP page which runs a small C# app that is multithreaded, which runs about 80 threads simultaneously, each one loading a PHP page which connects to the database. When I run it I get about 20 errors saying that it is unable to connect. I have done some tests and it seems to run fine if I only have about 30 threads running, but if I run 2 windows (ie 60 threads) it produces errors. Here is my php.ini file relating to MSSQL: [MSSQL] ; Allow or prevent persistent links. mssql.allow_persistent = Off ; Maximum number of persistent links. -1 means no limit. mssql.max_persistent = -1 ; Maximum number of links (persistent+non persistent). -1 means no limit. mssql.max_links = -1 ; Minimum error severity to display. mssql.min_error_severity = 10 ; Minimum message severity to display. mssql.min_message_severity = 10 ; Compatibility mode with old versions of PHP 3.0. mssql.compatability_mode = Off ; Connect timeout mssql.connect_timeout = 10 ; Query timeout mssql.timeout = 30 ; Valid range 0 - 2147483647. Default = 4096. ;mssql.textlimit = 4096 ; Valid range 0 - 2147483647. Default = 4096. ;mssql.textsize = 4096 ; Limits the number of records in each batch. 0 = all records in one batch. mssql.batchsize = 0 ; Specify how datetime and datetim4 columns are returned ; On => Returns data converted to SQL server settings ; Off => Returns values as YYYY-MM-DD hh:mm:ss ;mssql.datetimeconvert = On ; Use NT authentication when connecting to the server mssql.secure_connection = Off ; Specify max number of processes. -1 = library default ; msdlib defaults to 25 ; FreeTDS defaults to 4096 mssql.max_procs = -1 ; Specify client character set. ; If empty or not set the client charset from freetds.comf is used ; This is only used when compiled with FreeTDS ;mssql.charset = "ISO-8859-1" My setup is: Windows Server 2003 SP2 SQL Server 2005 Express PHP 5.2.0 IIS 6 Using the ntwdblib.dll extension I assume that MSSQL can handle much more than 60 simultaneous connections to the database, and PHP looks like it is not limiting the connections either. Is there something else vital I am missing in this whole thing? Any help is much appreciated, thanks Dylan
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.