php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #33765 SOAP one-way is not fire-and-forget
Submitted: 2005-07-19 09:20 UTC Modified: 2005-10-11 18:01 UTC
Votes:5
Avg. Score:4.4 ± 0.8
Reproduced:5 of 5 (100.0%)
Same Version:3 (60.0%)
Same OS:3 (60.0%)
From: php at sowen dot de Assigned: dmitry (profile)
Status: Wont fix Package: SOAP related
PHP Version: 5.1.0b3 OS: Gentoo Linux
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: php at sowen dot de
New email:
PHP Version: OS:

 

 [2005-07-19 09:20 UTC] php at sowen dot de
Description:
------------
When I try to make a SOAP call to a server that doesn't reply with an answer, my client keeps on waiting until the server finished it's work. 

Shouldn't one-way operation be "fire-and-forget" in order to make more sense?

This could be solved by returning a HTTP 200 response and closing the socket, right after the SOAP call was received by the server.



Reproduce code:
---------------
Server code:
------------

public function onewaytest() {
   sleep(50);
}

Client code:
------------

$soap = new SoapClient(null, '...');
$starttime=time();
$soap->onewaytest();
echo time()-$starttime." sec\n";

Expected result:
----------------
Just the network time-overhead caused by HTTP connect and POST. 

Actual result:
--------------
Above 50 sec.

Patches

Pull Requests

 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Dec 22 01:01:30 2024 UTC