Andrei, I was agree with your patch only after 5.1.3 release. And I disagree with persistent WSDL by default at all. Especially without protection against huge memory usage. I hadn't time to look into you patch careful, and seems it wasn't tested enough. I looked into it today, found and fixed another bugs in addition to your fix. I cannot be sure that these are latest bugs related to this patch. Also for what reason you disabled disk cache? I re-enabled it. Thanks. Dmitry. > -----Original Message----- > From: Andrei Zmievski [mailto:andrei@gravitonic.com] > Sent: Monday, April 17, 2006 8:13 PM > To: Dmitry Stogov > Cc: Uwe Schindler; soap@lists.php.net; Rasmus Lerdorf > Subject: Re: Frequent crashes in multithreaded > webserver since new WSDLcaching code in ext/soap > > > Dmitry, > > Please don't commit things to the code from under me.. If you read > the comments, you would see that I fixed the serious crash that was > occuring and was working on that fixing the other one. > > -Andrei > > > On Apr 17, 2006, at 6:19 AM, Dmitry Stogov wrote: > > > Hi Uwe, > > > > I just fixed sevral bugs in new code and re-enabled disk > cache. Could > > you test CVS version (or snapshot)? > > > > Thanks. Dmitry. > > > >> -----Original Message----- > >> From: Uwe Schindler [mailto:thetaphi@php.net] > >> Sent: Friday, April 14, 2006 4:56 PM > >> To: andrei@php.net; soap@lists.php.net > >> Subject: Frequent crashes in multithreaded > webserver since new > >> WSDLcaching code in ext/soap > >> > >> > >> Hallo Andrei, > >> > >> yesterday I tried the newest PHP 5.1 snapshot on my SunONE > webserver > >> (I am the maintainer of the NSAPI SAPI code). This webserver is > >> multithreaded so your new WSDL caching code in ext/soap > should work > >> great. But it doesn't. > >> > >> The first call to a php script that uses SoapClient works correct > >> (everytime). Further requests to the same script crash the > webserver > >> with SIGSERV, SIGBUS, etc. > >> > >> Here are some different the crashs I have seen yesterday. > The problem > >> is that it happens at totally different locations, most > times there > >> is not even a core dump available that can be analyzed (stack is > >> corrupt so no dump availabe): > >> > >> [13/Apr/2006:16:49:35] info (25237): CORE3261: Crash occurred in > >> NSAPI SAF php5_execute > >> > >> [13/Apr/2006:18:38:15] info ( 8381): CORE3261: Crash occurred in > >> NSAPI SAF php5_execute [13/Apr/2006:18:38:15] info ( > 8381): CORE3262: > >> Crash occurred in function master_to_xml from module > >> /pangaea/webserver61/bin/ libphp5.so > >> > >> [13/Apr/2006:18:44:03] info (11702): CORE3261: Crash occurred in > >> NSAPI SAF php5_execute [13/Apr/2006:18:44:03] info > (11702): CORE3262: > >> Crash occurred in function encode_reset_ns from module > >> /pangaea/webserver61/bin/libphp5.so > >> > >> [13/Apr/2006:19:02:17] info (12182): CORE3261: Crash occurred in > >> NSAPI SAF php5_execute [13/Apr/2006:19:02:17] info > (12182): CORE3262: > >> Crash occurred in function strcmp from module /usr/lib/libc.so.1 > >> > >> [13/Apr/2006:20:02:13] info ( 1965): CORE3261: Crash occurred in > >> NSAPI SAF php5_execute [13/Apr/2006:20:02:13] info ( > 1965): CORE3262: > >> Crash occurred in function encode_reset_ns from module > >> /pangaea/webserver61/bin/libphp5.so > >> > >> [13/Apr/2006:20:04:37] info ( 3221): CORE3261: Crash occurred in > >> NSAPI SAF php5_execute [13/Apr/2006:20:04:37] info ( > 3221): CORE3262: > >> Crash occurred in function whiteSpace_collapse from module > >> /pangaea/webserver61/bin/libphp5.so > >> > >> [13/Apr/2006:20:13:10] info ( 5916): CORE3261: Crash occurred in > >> NSAPI SAF php5_execute [13/Apr/2006:20:13:10] info ( > 5916): CORE3262: > >> Crash occurred in function whiteSpace_collapse from module > >> /pangaea/webserver61/bin/libphp5.so > >> > >> When I disable soap.wsdl-cache completely, everything works again > >> without any crash. I have seen that wirth the new code no longer > >> /tmp/wsdl-XXXXX files are generated. Is there a > possibility to switch > >> to the older file-based caching code? For eaxample as > enumeration in > >> the wsdl-cache php.ini configuration option? Is there any other > >> possibility to disable the wsdl cache code without undoing > a lot of > >> soap patches? I want to update the webserver because of security > >> reasons to latest snapshot. > >> > >> Do you have similar problems with other webservers that are > >> multithreaded? Sorry that I cannot give more helpful > information (the > >> crashes are totally different and the corefiles are mostly > useless). > >> > >> ----- > >> Uwe Schindler > >> thetaphi@php.net - http://www.php.net > >> NSAPI SAPI developer > >> Bremen, Germany > >> > > > > -- > PHP Soap Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > > -- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
