Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

read socket time out exception in SOAP UI

former_member185489
Participant
0 Likes
1,141

Hi all,

I am trying to debug a webservice on client system using SOAP UI. Using the SOA Manager I have downloaded the WSDL file and am able to see the exceptions being raised in reponse.

However while trying to debug it I am getting a read socket time out exception and no reponse is getitng genrated. I am setting an external break point in the FM. Have set the timeout in the request properties to 60000 and also the socket time out to 1000000 under File->Preferences->Socket time out. after changing the values in debugging, However there is no reponse generated and am getitng the same socket time out error. Any ideas on what else chanegs we need to do to prevent the error and get the response?

Thanks in advance!!

regards,

Suman

Hi all,

I am trying to debug a webservice on client system using SOAP UI. Using the SOA Manager I have downloaded the WSDL file and am able to see the exceptions being raised in reponse.

However while trying to debug it I am getting a read socket time out exception and no reponse is getitng genrated. I am setting an external break point in the FM. Have set the timeout in the request properties to 60000 and also the socket time out to 1000000 under File->Preferences->Socket time out. after changing the values in debugging, However there is no reponse generated and am getitng the same socket time out error. Any ideas on what else chanegs we need to do to prevent the error and get the response?

Thanks in advance!!

regards,

Suman

2 REPLIES 2
Read only

Former Member
0 Likes
785

Hi Suman Biswas,

I know your Problem is quite old,

but I am facing the same Problem (not sure) right now

Do you know any solution? or anyone else?

BR

Mike

Read only

0 Likes
785

Hi Michael,

Yes, it was solved! we just increased the socket time out time. Turns out it was in micro seconds!! try increasing the socket time and see if it works!!

Regards,

Suman