Hi everyone,
I am using a PB Web Service Proxy (using .NET rather than EasySoap) to consume a C# provided SOAP Webservice, pulling service definitions via the WSDL.
This service was originally called over HTTP and it all worked without issue. It was also nearly instant for most calls.
I have since moved this over to using the same service except it is now called over HTTPS. The calls to the service still work but they are extremely slow.
(30-60 seconds for even small responses, where as previously they were nearly instant).
I have called the same SOAP service using SoapUI and from a C# .Net desktop application using HTTPS and results are instant, with no difference between that and the HTTP calls.
Has anyone had this issue and is there anything I should be looking at to correct this issue?
Thanks for any help given,
Alan
The create connection and create instance are instant with the entire delay when calling the proxy method.
Edited down version:
SoapConnection conn // Define SoapConnection
long ll_conn_result, ll_log
string ls_containers
conn = create SoapConnection // Instantiated connection INSTANT
ll_log = conn.SetSoapLogFile ("C:\mySoapLog.log") // Set trace file to record soap interchange data,
// if string is "", disables the feature
ll_conn_result = Conn.CreateInstance(i_n_my_service_services,"myservice") // INSTANT
// Create proxy object
try
i_baseuriinfo = i_n_my_service_services.do_stuff(i_s_api_key) // ENTIRE DELAY HERE
catch ( SoapException e )
MessageBox ("Error", "Cannot invoke Web service: " + e.text)
end try
destroy conn
I may accept a slow first call because the data type de-serialization, but 30-60 secs is actually too much for a WS call if the Soap connection is done.
What if you run the client from PB 2017? That would help to reproduce the problem.
Cheers,
Marco
Yes I tried a test app with PB2017 and it works in this without issue even with HTTPS.
Thanks,
Alan