Forum Discussion

darylrobertson's avatar
11 years ago

[LoadUIWeb] Errors: Unable to decrypt SSL data from the server. Context expired.

I've just started looking into load testing tools and this is the first one that I decided to try.



Everything looks very clean and easy to use but I cannot seem to get a script to verify.



I've attempted to record the script upwards of 10 times and each time I get a varying number of errors.



The error is as follows (There were 10 of them in this iteration of the script):




Request #1 of the virtual user "Virtual user (1)" simulating the scenario "Scenario1" failed. Unable to decrypt SSL data from the server. Context expired.






I've done some looking and have seen references to people having problems with SSL errors but haven't seen any related to 'Context expired'



Can someone give me an idea how to work through this? I can provide additional information if required.

4 Replies

  • I see this happen most often when a session tracking variable or critical parameter is not included in the recording for one reason or another.

    Most commonly, the JSESSIONID or other custom, app-specific parameters to a request causes the server to return either a 400 (bad request) or 500 (internal server error) because it does not understand the request without proper parameters. Many times, a "context expired" SSL related message means that the server sent either no data or a partial error message back to the client because it did not provide the proper session or parameters in the request.

    It is often resolved by going back and examining what was [not] posted in the specific request. If you right-click the failed message log item and select 'open associated request in editor...', then look at the Request > Form > Parameters and other related components of the request, it may be posting static values that need to be dynamic for the server to respond successfully.

    Once you parameterize or adjust your request and then replay, make sure to have the Tools > Options > Engine > Simulation > "Store request bodies" preference enabled before you re-run the test. Now go back to the original request that was erroring out to see what's actually being posted. If your adjustment corrected the issue, you should no longer receive this error message.
  • MPunsky's avatar
    MPunsky
    SmartBear Alumni (Retired)
    Hello D.R.,



    What version of LoadUIWeb are you testing with?

    What browser/version did you use to record the scenario?



  • Hi,



    I m also facing the same error.



    The version I m using is LoadUI Web 9.02 & the browser is IE 8