windows - PHP Pthreads latest version 3.1.6 (64bit) not installing on Apache -
i trying install latest pthreads extension 3.1.6 64bit php.
as per author advice of pthreads, on http://github.com/krakjoe/pthreads
i have placed 2 dlls desired locations.
add pthreadvc2.dll (included windows releases) same directory php.exe eg. c:\apache24\php add php_pthreads.dll php extention folder eg. c:\apache\php\ext
and in windows\system32 directory
and added loadfile in [apache http.confd][1]
and have added added extension php.ini
but apache won't start , when check apache error.log, have below
[tue jun 28 11:38:31.184618 2016] [ssl:warn] [pid 8640:tid 352] ah01909: localhost:443:0 server certificate not include id matches server name
[tue jun 28 11:38:31.215819 2016] [core:warn] [pid 8640:tid 352] ah00098: pid file c:/apache24/logs/httpd.pid overwritten -- unclean shutdown of previous apache run?
i have moved php_pthreads.dll extension top of extension list , bottom no joy. won't start pthreads dll. if comment ;extension=php_pthreads.dll , apache restart not pthreads dll.
is bug or doing wrong?
little info of system setup window 7 64 bit, apache 2.4.x vc14
php info
system windows nt ng10676 6.1 build 7601
(windows 7 enterprise edition service pack 1) amd64
build date jun 21 2016 15:08:19
compiler msvc14 (visual c++ 2015)
architecture x64
thread safety enabled
please note have vc compilers installed on system 10, 11, 14 64 bit , installed 32 bit in case.
please note, have tried previous threads pthreads installation , don't installation. have tried every google page don't work, appreciated. if php pthreads designer can shed light on version.
pthreads v3 restricted operating in cli only: have spent many years trying explain threads in web server don't make sense, after 1,111 commits pthreads have realised that, advice going unheeded.
so i'm promoting advice hard , fast fact: can't use pthreads safely , sensibly anywhere cli.
thanks listening ;)
quote blog explaining change v2
...
ejb's expressly prohibit programmer creating threads specification, , modern java doesn't have 1:1 model. obviously, because environment may migrated (moved within cluster of servers), moving threads outside of it's managed pool difficult imagine. goes further prohibiting creation of threads though, prohibits use of synchronization primitives, because if node moved while retain lock - hell breaks loose.
in java generally, discouraged manually creating threads in servlets, same reasons have discouraged pthreads.
while it's true not every environment prohibit it, runs deep can be; agrees creating real (1:1) threads in web response context bad idea.
...
Comments
Post a Comment