|
|
Re: [SOAP] soapcall.invoke() runs up to 20 seconds before sending request : msg#00038
mozilla.devel.xml
|
Subject: |
Re: [SOAP] soapcall.invoke() runs up to 20 seconds before sending request to server |
markus siebeneicher wrote:
hallo list,
hope this is the right place to post this SOAP-related question. so, i
have build up a remote script with an soap-client which request to an
soap-server based on php. this is my code to use the soap-web-service on
my intranet-server:
var method = "test";
var service = "uri:xfibel";
var mySOAPcall = new SOAPCall();
mySOAPcall.transportURI =
"http://intranet/intranet-dev/unstable/bundle/xfibel/api/xfibel-handler.php";
var myParams = new Array();
myParams[0] = new SOAPParameter("Hello World!", "value");
mySOAPcall.encode(0, method, service, 0, null, myParams.length,
myParams);
var myAnswer = mySOAPcall.invoke();
if (myAnswer.fault) {
alert(myAnswer.fault.faultString);
return false;
} else {
var num = new Object();
var params = myAnswer.getParameters(false, num);
return params[0].value;
}
here is my php-code:
<?php
# php5.0.0
# using php-soap-extension
function test($value) {
return $value;
}
$server = new SoapServer(null, array('uri' => "xfibel"));
$server->addFunction("test");
$server->handle();
?>
so, the problem is that the script runs till the invoke() method, than
seems to hang or executing something(maybe some xml serializing?), that
needs up to 20 seconds and then receive the message from the server and
returns it without(!) any error. the result is as expected!
i checked out if the server was running in the right manner, i request
the php service with an other client(php-script) and get the response
immediatly and without error. i also logged the execution-time of the
server process for both, the php-client and the mozilla/firefox-client.
no difference found. however, the problem seems to be on the
mozilla/firefox-client side.
unfortunately my knowledge about the soap and http internernals are
minimal. my guess is, that in the http connection area something goes
wrong or in other words: pretty slow. is there a way(class) to monitor
the http request which are send by the soap component(invoke or
asyncinvoke)? by the way, asyncinvoke() runs also slow.
is anyone out there which runs under the same problem and get out of the
blog?
many thanks for any notes and suggestionens!
regards, markus siebeneicher
the problem is still there, but i found out now, that the process which
is running up to 20 seconds runs AFTER the requested soap-message from
the soap-server. i noticed that when the server writes the log file(of
the soap-process) immediatly after clicking on my
mozilla/firefox-get-soap-button.
so, if there is anyone who knows what the soap-handler is working on
after requesting the message from the server pls enlight me.
markus siebeneicher
|
|