your php module is not compiled to be thread safe suse

If you still insist on using ISAPI implementations, you should probably use the latest versions of the PHP4 distribution instead. The moral of the story is that PHP isn’t multi-threaded – yet if you go by what they say, you’d come to think it was… until you try it out for yourself and realize that not a darn thing has changed in the 5.2.x releases when it comes to thread-safety and the deployment of PHP in multi-threaded environments. But we’ve already discussed this before, countless times. Whether on Linux or Windows, FastCGI scripting engines are considerably faster than their age-old CGI implementations (though the outcome is more-clearly felt on Windows where the CGI model is hideously slow). Unfortunately, there’s not much more to be said making this post more of a rant than a guiding light for those of you experiencing this issue.Īt NeoSmart Technologies we still recommend the only other production-ready, decently-performing *sapi alternative which is the deployment of PHP by means of the FastCGI protocol. It’s filled with race conditions and lacks the proper monitors/locks on shared memory spaces (which needn’t be shared in the first place). The source code for the official PHP distribution is simply not re-entrant and isn’t capable of being used in multi-threaded environments. There isn’t a known solution to this problem. PHP isn’t multi-threading ready and most everyone knows it… but it seems they still feel the need to pass it off as if it were, never mind the complaints and bug reports that come. It’s not a question of server configuration so much as it is one of PHP writing bad code and pretending that’s not the case.

You’ll still get the same, old, dreaded “PHP has encountered an access violation at memory_address” error. The problem is, no matter which you choose, PHP isn’t thread safe. If you look at the PHP download page, you’ll see that the pre-built binaries (in this case, Windows) are split into two: thread-safe and non-thread-safe:

nothing more than a bunch of lies, if you will. Don’t attempt to use PHP in a multi-threaded environment (mpm_worker on Apache, ISAPI on IIS, etc.), because PHP thread-safety is a myth. If you took everything you heard for granted, you’d have been lead to believe that the official PHP distributions (from php.net) have been thread-safe since version 5.2.0.

Your php module is not compiled to be thread safe suse