How to get pthreads working in PHP?

Question

I am using wampserver to test & run wordpress code in my local computer. In order to run pthread, I have followed the following steps:

1) I got the pthread zip f

Answer 1

You have to add a require_once() with the path of the Thread class before extending it (if your framework don't use an autoload class system)

Answer 2

I've noticed that wampserver has php.ini in two separate places. One place is in the /wamp/bin/php/php5... directory, and the other place is in the /wamp/bin/apache/apache.../bin directory (where "..." represents version numbers). The two files need to be identical, because apparently both are loaded at different times by the overall wampserver boot-up procedure.

(Note I only discovered this recently, and may be well "behind the curve" of doing fancy things with wampserver --maybe everyone else has been dealing with both files for a long time. So I don't know if this simple thing will fix your problem; I came here looking for info, myself, regarding doing some multi-threading stuff. :)

One other thing. According to this page: www.php.net/manual/en/pthreads.requirements.php PHP has to be compiled with "--enable-zts" in order for pthreads stuff to work. I have not been able to find any evidence that the PHP part of wampserver was compiled that way.

---

(months later) Having decided I didn't really immediately need to do any threading stuff, I went on to do other things, until the need actually arose. I now can say that the version of PHP compiled into WampServer does support the "pthread" extension, although some set-up work is needed, first. The instructions I saw mentioned putting a couple of .dll files (after a download and unZip) into certain places, but that didn't work for me. Copying them to the \Windows\System32 directory did work. (Putting them into the \apache...\bin directory also works; there are some other php .dll files in there.)

After that, much like what you did, it is necessary to define a "class" that extends the "Thread" class, in order to actually do something in another thread. The "run()" function in the Thread class is "abstract", and needs to be "realized" as an actual function in the extended class. Then the "new" operator can create an "instance", an object of that specified class, for actual use. Here's the class that I needed:

//Purpose: Use another thread to run the code in another php file, after a delay
class xT extends Thread
{ var $fil, $tim;

  function savWhatWhen($f="", $t=0)
  { $this->fil = $f;                    //save What, file to process
    $this->tim = $t;                    //save When, delay before processing file
    return;
  }

  function run()
  { ini_set('max_execution_time', 600); //600 seconds = 10 minutes
    sleep($this->tim);                  //do a delay; beware of max-exec-time!
    include($this->fil);                //load file-to-process, and process it
    return;
} }

That "savWhatWhen()" function was created specifically for this extension of the basic Thread class. Here's some code for using that class:

  $TH = new xT();                                    //prepare a separate Thread
  $TH->savWhatWhen("d:/wamp/myscripts/test.php", 45);//file-name and delay time
  $TH->start();                                      //after delay, process file
  //the code that does this can terminate, while OTHER thread is doing a delay

Note for anyone copying this code, you might need to make sure your "open_basedir" setting in the php.ini allows access to the specified file.

---

More months later: With lots of things being worked on, I haven't put a lot of time into using my pthread object. I did encounter a peculiarity that makes me wonder about whether or not I can actually use pthreads the way I had hoped. Here is what I have observed: 1. An initial php file is called by AJAX, to do something. 2. The PHP processor on the Web Server does that thing. 3. Various data is supposed to be echoed to the browser. 4. The initial php file calls for the creation of another thread, and terminates. 5. The browser does not yet receive the echoed data! 6. The PHP processor on the Web Server does the work delegated to the second thread. 7. When the second thread terminates, NOW the browser receives the echoed data!

At this writing I'm thinking I missed something. Perhaps I need to do some forceful "flush" stuff when the first thread ends, so that the browser can receive the echoed data and the user can do things while the PHP processor on the server is also doing things.

Answer 3

Wamp server has a separate php.ini config file for the browser and for the cli.

To use the pthreads module in the browser with WAMP Server you need to copy the "pthreadVC2.dll" into the apache "bin" directory also.

You should now have he "pthreadVC2.dll" in both of these folders (if installed in default location):

C:\wamp\bin\php\php[x.x.xx]\bin
C:\wamp\bin\apache\apache[x.x.x]\bin

You will also need to update the php.ini file within the php bin directory AND the apache bin directory to include:

extension=php_pthreads.dll

This now means you can use pthreads in the browser and in the cli with wamp server

Answer 4

Check for extension_dir = "ext" in you php.ini file. Make sure it points to the folder where your extensions reside and make sure it's not commented (it has a semicolon ; in front of it)

Answer 5

After encountering the same problem, I noticed that I have installed the wrong Pthread version (3.1.6 : requires PHP7+) which wasn't compatible with my PHP version (5.5.12). Solved the problem with Pthread version 0.0.44. An earlier version should probably work well.

Here is the download page for Pthread and the installation page. Be careful about the both php.ini location as mentioned above (Apache folder=for Browser, PHP folder=CLI).

Answer 6

I've encountered the same problem, in my case placing the pthreadVC2.dll in

..wamp\bin\apache\Apache2.4.4\bin

(instead of ..\wamp\bin\php\php5.4.16 as the guide in php.net instructs) solved the problem