Forum Discussion
RFloyd2000
13 years agoOccasional Contributor
yes, after studying the behavior awhile with loadTest in soapUI, it appears you are correct. The desired behavior in soapUI is basically a fluke, since sometimes I am seeing the exact same behavior as loadUI.
Basically, I'm trying to emulate the behavior of Firefox, or Internet Explorer. When these browsers are used, they seem to select from the pool instead of using the same 1 or 2 connections all the time.
Since adding a feature such as this may be very involved, or may not even be possible....can you think of a workaround for us? Such as, the "script strategy", is there a way to create the test in such a way that multiple TCP connections would be made?
The only alternative I know of is to simply close the connection after each request, but that is the other extreme.
Basically, I'm trying to emulate the behavior of Firefox, or Internet Explorer. When these browsers are used, they seem to select from the pool instead of using the same 1 or 2 connections all the time.
Since adding a feature such as this may be very involved, or may not even be possible....can you think of a workaround for us? Such as, the "script strategy", is there a way to create the test in such a way that multiple TCP connections would be made?
The only alternative I know of is to simply close the connection after each request, but that is the other extreme.