php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #43556 SoapClient Segmentation fault on timeout
Submitted: 2007-12-10 21:42 UTC Modified: 2008-02-05 01:00 UTC
Votes:9
Avg. Score:4.7 ± 0.7
Reproduced:9 of 9 (100.0%)
Same Version:4 (44.4%)
Same OS:6 (66.7%)
From: mkaatman at gmail dot com Assigned:
Status: No Feedback Package: SOAP related
PHP Version: 5.2.5 OS: linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: mkaatman at gmail dot com
New email:
PHP Version: OS:

 

 [2007-12-10 21:42 UTC] mkaatman at gmail dot com
Description:
------------
Bug 33412 seems to have slipped back in.

Seeing it in ubuntu's 5.2.3-1ubuntu6.2 package and CentOS 5.2.4 package.

I've been able to reproduce it 100% of the time by running my requests through a proxy and just stopping the proxy.

Every subsequent request gives a notice in the apache2 log.

[Mon Dec 10 15:13:07 2007] [notice] child pid 11731 exit signal Segmentation fault (11)

Once I start the proxy back up everything works fine.


Reproduce code:
---------------
   try {
      $result = $soapclient->__soapCall($f,$p);
      print "Successful Call\n";
   } catch (SoapFault $exception) {
      print "SOAP EXCEPTION: $exception\n";
   }


Expected result:
----------------
No segfault. Normal SOAP timeout response.

Actual result:
--------------
[Mon Dec 10 15:13:07 2007] [notice] child pid 11731 exit signal Segmentation fault (11)


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2008-01-29 00:45 UTC] tony2001@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc. If the script requires a 
database to demonstrate the issue, please make sure it creates 
all necessary tables, stored procedures etc.

Please avoid embedding huge scripts into the report.


 [2008-02-05 01:00 UTC] 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".
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Apr 25 14:01:31 2024 UTC