Forum Discussion

RMS's avatar
RMS
Occasional Contributor
16 years ago

Re: Socket Time Out during loadtest

Hi,

I am currently using the sopa ui 2.5.1 (as could not install the 3.0.1 succesfully due to JAVE_HOME error as per my ealier post) to loadtest web service.

The TestCase has following steps which runs for 1 hour window and is repeated for 10 hour with different dataset.

1. Authenticate
2. Read DataSource (which reads xml files from a particular location and shared across multiple threads)
3. Transfer the xml file from Datasource to SAVE step
4. SAVE (which sends the xml file through web service to SAVE it in the SQL database)
5. Transfere the response from SAVE (account id) to Process step
6. Process step which processes the account id received from the step 5
7. Loop the DataSource

For the load test I am using the simple strategy with Test Delay of 20 mins with Random set to 1. The number of threads are set to half the number of limit (total runs)

Also the SocketTimeOut is set to 0 and Max response size is set to 0 in the SoauUI preferences.

It works fine except for some requests I am receiving following error message in the soap ui log files

Thu Aug 13 16:24:59 PDT 2009:Save:TestStep [Save] result status is FAILED; [java.lang.Exception: java.net.SocketTimeoutException: Read timed out]:8
----------------------------------------------------
Status: FAILED
Time Taken: 0
Size: 0
Timestamp: Thu Aug 13 16:24:59 PDT 2009
TestStep: Save
java.lang.Exception: java.net.SocketTimeoutException: Read timed out
----------------------------------------------------
Encoding: UTF-8
Endpoint: http://rblab9/services/account.asmx
Username: null
Password: null
Domain: null
---------------- Request ---------------------------

 

 
     
           
            0
            0
            Insert........

 

---------------- Response --------------------------
- missing response / garbage collected -

Can you please let us know how to fix this issue?

Thanks,

      --ag
  • RMS's avatar
    RMS
    Occasional Contributor
    16 years ago
    Hi,

    Sorry I should have alaborated more on the SAVE and Process step. These steps can take longer to response depending on the size of the xml file which it's trying to SAVE. The above error message was for xml file which is 16MB.

    Also I am assuming that setting the SocketTimeOut to 0 sets it to unlimited timeout.

    Thanks,

        --ag
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hi Amit,

    can you check the Socket Timeout setting at the TestCase level also (in the TestCase Options dialog), which should be 0?

    regards!

    /Ole
    eviware.com
  • RMS's avatar
    RMS
    Occasional Contributor
    16 years ago
    Hi,

    I just checked the TestCase options and all the below three parameters are set to 0

    1. Socket Time Out
    2. TestCase Time Out
    3. Max Results

    and the only check boxes which are unchecked are Session and Discard OK results.

    Let me know if I should look into something else also to fix this issue?

    Thank you so much for your prompt reply,

    Regards,

          --ag
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hello,

    Try setting socket time out on some really large value ( ex. 999999 ).

    Let me know does it helps,

    robert
  • RMS's avatar
    RMS
    Occasional Contributor
    16 years ago
    Hi,

    I tried the higher value also but no luck, In the process of trial and error, I tried checked the option which says Discard Successful results to preserve memory and it solved the issue for now.

    Thanks for your prompt replies,

          --ag