web service problem (Timeout)

[Former Member]

hello

i hope this is the right category to post my problem

i want to use the service "customerCRMChangeRequestConfirmation_In"

but i get this error message: "Error getting response; java.net SocketTimeoutException: Read timed out.

on my search to fix this problem i found the SAP Note 826419.

with following advice:

===========================================================================================

Version NW 7.10

• Using NetWeaver Administrator

o For standard Web service deployable proxy:

1. Open SAP NetWeaver Administrator in a browser: http:// "Web Services Administration".

3. Choose "Proxy Definitions by Name" and click "GO".

4. Select the proxy you want to configure.

5. Choose the "Configuration" tab.

6. Choose the "Logical Ports" tab.

7. Select the logical port you want to configure and choose "Edit".

8. Choose the "Transport Settings" tab.

9. Edit the "Max wait-time for HTTP response (in milliseconds)" field.

10. Click "Save" to save the settings.

============================================================================================

but in my Transport Settings are no "May wait-Time for HTTP response-field"

what is the problem? i have an SAP CRM IDES System with Netweaver 7.1

do I need to install an sp?

I also found this solution for my read time out problem:

http://wiki.sdn.sap.com/wiki/display/TechTSG/%28WSR%29Problems-P01

but this solution with "Visual Administrator" is for java stack, right?

thank you for your help!

kind regards

sven möller

[Former Member · Accepted solution]

can anyone help me?

[Former Member · Accepted solution]

Hi Sven,

I just have a couple more suggestions, otherwise I'm stumped:

but the system worked long on this change process

How long did this take?

You could try turning on the ICF Recorder using the 'Request & Response' radio button for the user you're using in SoapUI (Google for correct usage on help.sap.com). This will log the request as it came in from SoapUI and the reponse that would be generated by IDES ECC even if SoapUI times out. Then trigger your call from SoapUI. Wait for the response to complete in IDES ECC, by that time SoapUI would have timed out. Then in IDES ECC, display the 'Table Entry' drop down menu option (with the glasses) for the ICF Recording of your SoapUI request + response. Then do a comparison against the logon timestamp & the response timestamp to see how long it actually took. Then maybe try increasing the SoapUI timeout parameter accordingly.

Otherwise, you'll probably need to post another question in maybe the SAP Netweaver Platform forum. They can guide you a bit more on the memory usage & tracing long running transactions. There could be something that helps you to isolate other performance issues. Personally, 5GB swap is unusually high.

Regards, Trevor