Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.

Getting 443 Connection timed out while running soatest and recording traffic via proxy

Options
kseniia
kseniia Posts: 13 ✭
in Virtualize

I have a soatest tst which works just fine.
I want to virtualize the endpoint that soatest tst exercises. I setup a proxy on my localhost and updated my tst to run the same request through the proxy. It responds with org.apache.http.conn.HttpHostConnectException: Connect to failed: Connection timed out: connect.
What could be a reason for that response?

Answers

  • kaustin
    kaustin Posts: 4 admin
    Options

    A likely reason is that the proxy is not reachable on the host/port your test is using, or the proxy service is not running.

    From the documentation, SOAtest/Virtualize proxy-based traffic handling depends on the local web proxy being available. In the Recorder documentation, Parasoft notes that the SOAtest Web Proxy must be running and that port 40090 must be available for the web proxy to run.

    Also, if you are using HTTPS through a proxy, the proxy settings must be configured correctly. At minimum, the documented properties are:

    https.proxySet=true
    https.proxyHost=[hostname]
    https.proxyPort=[port number]
    If the proxy requires authentication, the documented credentials properties are:

    https.proxyUser
    https.proxyPassword
    If you are relying on system proxy settings, the documentation says to enable:

    java.net.useSystemProxies=true

Categories