#34657 [Bgs-Csd]: If you get a communication problem when loading the WSDL, it fatal's
ID: 34657
User updated by: gareth at wsys dot co dot uk
Reported By: gareth at wsys dot co dot uk
-Status: Bogus
+Status: Closed
Bug Type: SOAP related
Operating System: Windows, Linux
PHP Version: 5.1.6
Assigned To: dmitry
New Comment:
OK, the debug information shows that the Soap client class is now
throwing an uncaught SoapFault exception (which causes the fatal
error).
with a try{ } catch(SoapFault $exception) I can continue the script.
I've closed the bug.
Previous Comments:
[2006-09-12 08:56:12] [EMAIL PROTECTED]
I cannot reproduce the bug even with 5.1.4. Try php -d log_errors=0
test.php. May be you are seeing log message and don't see Error
Caught after it?
[2006-09-11 07:50:34] gareth at wsys dot co dot uk
I have tried to use set_error_handler(), but as you know it cannot
catch fatal errors.
Does anyone else have a workaround?
[2006-09-08 21:50:38] [EMAIL PROTECTED]
See also bug #38703.
[2006-09-06 10:40:10] gareth at wsys dot co dot uk
Have tried on PHP version 5.1.6, still getting the following error:
Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from
'http://urlhere.com/file.wsdl'.
So I still cannot catch this error, which limits my use of SOAP as it
will kill my script.
[2006-09-05 12:32:44] [EMAIL PROTECTED]
Seems this bug was already fixed in CVS HEAD, PHP_5_2 and PHP_5_1 long
time ago.
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/34657
--
Edit this bug report at http://bugs.php.net/?id=34657edit=1
#34657 [Opn]: If you get a communication problem when loading the WSDL, it fatal's
ID: 34657 User updated by: gareth at wsys dot co dot uk Reported By: gareth at wsys dot co dot uk Status: Open Bug Type: SOAP related Operating System: Windows, Linux PHP Version: 5.1.6 Assigned To: dmitry New Comment: I have tried to use set_error_handler(), but as you know it cannot catch fatal errors. Does anyone else have a workaround? Previous Comments: [2006-09-08 21:50:38] [EMAIL PROTECTED] See also bug #38703. [2006-09-06 10:40:10] gareth at wsys dot co dot uk Have tried on PHP version 5.1.6, still getting the following error: Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://urlhere.com/file.wsdl'. So I still cannot catch this error, which limits my use of SOAP as it will kill my script. [2006-09-05 12:32:44] [EMAIL PROTECTED] Seems this bug was already fixed in CVS HEAD, PHP_5_2 and PHP_5_1 long time ago. [2006-01-14 12:08:16] [EMAIL PROTECTED] Assigned to the maintainer. [2006-01-13 14:20:13] gareth at wsys dot co dot uk The only solution I have come up with for this problem is to put the SOAP call into a seperate php file and then use it with exec(). This does however limit the input/output options available. The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/34657 -- Edit this bug report at http://bugs.php.net/?id=34657edit=1
#34657 [Csd-Opn]: If you get a communication problem when loading the WSDL, it fatal's
ID: 34657 User updated by: gareth at wsys dot co dot uk Reported By: gareth at wsys dot co dot uk -Status: Closed +Status: Open Bug Type: SOAP related Operating System: Windows, Linux -PHP Version: 5.1.2 +PHP Version: 5.1.6 Assigned To: dmitry New Comment: Have tried on PHP version 5.1.6, still getting the following error: Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://urlhere.com/file.wsdl'. So I still cannot catch this error, which limits my use of SOAP as it will kill my script. Previous Comments: [2006-09-05 12:32:44] [EMAIL PROTECTED] Seems this bug was already fixed in CVS HEAD, PHP_5_2 and PHP_5_1 long time ago. [2006-01-14 12:08:16] [EMAIL PROTECTED] Assigned to the maintainer. [2006-01-13 14:20:13] gareth at wsys dot co dot uk The only solution I have come up with for this problem is to put the SOAP call into a seperate php file and then use it with exec(). This does however limit the input/output options available. [2005-09-28 08:40:33] garadox47 at ntlworld dot com I have tried the latest window version you provided a link to, it still throws an uncatchable fatal error. [2005-09-27 19:07:37] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/34657 -- Edit this bug report at http://bugs.php.net/?id=34657edit=1
#34657 [NoF-Opn]: If you get a communication problem when loading the WSDL, it fatal's
ID: 34657
User updated by: gareth at wsys dot co dot uk
Reported By: gareth at wsys dot co dot uk
-Status: No Feedback
+Status: Open
Bug Type: SOAP related
Operating System: Windows, Linux
PHP Version: 5.0.5
New Comment:
The only solution I have come up with for this problem is to put the
SOAP call into a seperate php file and then use it with exec().
This does however limit the input/output options available.
Previous Comments:
[2005-10-05 01:00:09] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to Open.
[2005-09-28 08:40:33] garadox47 at ntlworld dot com
I have tried the latest window version you provided a link to, it still
throws an uncatchable fatal error.
[2005-09-27 19:07:37] [EMAIL PROTECTED]
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
[2005-09-27 14:32:25] gareth at wsys dot co dot uk
Description:
When using the SOAP Client, it normally throws a catchable SoapFault
exception. This helps to elegantly fail if there is a problem with a
Web Service.
However, if the problem occurs when loading the WSDL, it throws a PHP
Fatal Error, which cannot be caught.
This means that if you want to use a web service in a web application,
you cannot handle the error (e.g. there is network congestion, or the
server hosting the web service goes down).
Is this intentional, I am not sure.
If it is intentional (and I hope not given the fact that you are
requesting information from a completely different server, not under
your control), any chance this can be changed to throw either a
SoapFault Exception, or just something that can be caught?
Reproduce code:
---
try {
$sc = new SoapClient(some.wsdl, array());
} catch (Exception $e) {
echo 'Error Caught';
}
Expected result:
Error Caught
Actual result:
--
Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from '{URL
Removed}'
--
Edit this bug report at http://bugs.php.net/?id=34657edit=1
#34657 [NEW]: If you get a communication problem when loading the WSDL, it fatal's
From: gareth at wsys dot co dot uk
Operating system: Windows, Linux
PHP version: 5.0.5
PHP Bug Type: SOAP related
Bug description: If you get a communication problem when loading the WSDL, it
fatal's
Description:
When using the SOAP Client, it normally throws a catchable SoapFault
exception. This helps to elegantly fail if there is a problem with a Web
Service.
However, if the problem occurs when loading the WSDL, it throws a PHP
Fatal Error, which cannot be caught.
This means that if you want to use a web service in a web application, you
cannot handle the error (e.g. there is network congestion, or the server
hosting the web service goes down).
Is this intentional, I am not sure.
If it is intentional (and I hope not given the fact that you are
requesting information from a completely different server, not under your
control), any chance this can be changed to throw either a SoapFault
Exception, or just something that can be caught?
Reproduce code:
---
try {
$sc = new SoapClient(some.wsdl, array());
} catch (Exception $e) {
echo 'Error Caught';
}
Expected result:
Error Caught
Actual result:
--
Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from '{URL Removed}'
--
Edit bug report at http://bugs.php.net/?id=34657edit=1
--
Try a CVS snapshot (php4): http://bugs.php.net/fix.php?id=34657r=trysnapshot4
Try a CVS snapshot (php5.0):
http://bugs.php.net/fix.php?id=34657r=trysnapshot50
Try a CVS snapshot (php5.1):
http://bugs.php.net/fix.php?id=34657r=trysnapshot51
Fixed in CVS:http://bugs.php.net/fix.php?id=34657r=fixedcvs
Fixed in release:http://bugs.php.net/fix.php?id=34657r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=34657r=needtrace
Need Reproduce Script: http://bugs.php.net/fix.php?id=34657r=needscript
Try newer version: http://bugs.php.net/fix.php?id=34657r=oldversion
Not developer issue: http://bugs.php.net/fix.php?id=34657r=support
Expected behavior: http://bugs.php.net/fix.php?id=34657r=notwrong
Not enough info:
http://bugs.php.net/fix.php?id=34657r=notenoughinfo
Submitted twice:
http://bugs.php.net/fix.php?id=34657r=submittedtwice
register_globals:http://bugs.php.net/fix.php?id=34657r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=34657r=php3
Daylight Savings:http://bugs.php.net/fix.php?id=34657r=dst
IIS Stability: http://bugs.php.net/fix.php?id=34657r=isapi
Install GNU Sed: http://bugs.php.net/fix.php?id=34657r=gnused
Floating point limitations: http://bugs.php.net/fix.php?id=34657r=float
No Zend Extensions: http://bugs.php.net/fix.php?id=34657r=nozend
MySQL Configuration Error: http://bugs.php.net/fix.php?id=34657r=mysqlcfg
