Why are unused sockets created during load test?

LegacyForumLegacyForum ✭✭Posts: 1,669 ✭✭
edited December 2016 in Load Test
It happens several times during the test that the tool connects to the server but never sends anything in the socket.
Tagged:

Comments

  • LegacyForumLegacyForum ✭✭ Posts: 1,669 ✭✭
    edited December 2010
    During load testing the LoadTest "pings" the server(s) on which it invokes web services by periodically establishing HTTP connections to the service endpoints. The connection establishment time is used as an approximation of the network time that appears in the load test report. If this behavior is not desired, the pinger can be disabled. To do that put the attached script into "startup" directory in SOAtest/LoadTest installation root.

    disablePing.py contents:
    ---------------------------
    from webtool.site import Pinger

    Pinger.setEnabled(0)
    print 'Pinger disabled'
    ---------------------------
  • LegacyForumLegacyForum ✭✭ Posts: 1,669 ✭✭
    I'd just like to point out that this can also be the cause of the error "javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake" on the server side during Load Test runs. The same solution above may be utilized to correct there errors.
  • LegacyForumLegacyForum ✭✭ Posts: 1,669 ✭✭
    edited June 2012
    The script mentioned above is supposed to disable Load Test's pinger which is what makes the dummy HTTP test connections. You can run the script from an Extension tool as a setup test. You can also put the script in the "startup" directory in the SOAtest/LoadTest installation root. The startup folder is actually under:

    <soatest_install>/eclipse/plugins/com.parasoft.xtest.libs.web_{ver}/root/startup.

    You can create the "startup" folder in that libs.web/root folder if it isn't there.
Sign In or Register to comment.