Q7

Runner behavior in environments with Http Proxy Servers

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.3.3
  • Fix Version/s: 1.3.5
  • Component/s: Licensing, Runner
  • Labels:
  • Test Mode:
    Manual

Description

Hey folks, excerpt from customer email:

Q7 Runner also works as expected, but currently I have some difficulties with running it on our build server: it is not able to connect to your license server. When I run the test on the same machine as an administrator, specifying the necessary JVM parameters (https.proxyPort and https.proxyHost), everything works fine. However, when I run it on our Hudson build server (which is being run by a Glassfish 3 service, logged in with my user account), it fails to connect to the license server. When trying to start the AUT, it prints the following message: "Q7 License server is unreachable, shutting down." The odd thing is that without the JVM parameters mentioned above, Q7 Runner stops right after printing its version number, and logs the same error message. It seems like Q7 Runner tries to connect to the license server two times: first when it starts up, then when it starts the AUT, On the first attempt, it succeeds with the connection, while on the second attempt, it fails.

Do we need a better reporting as well as do we pass https.proxy* parameters to the AUT?

Activity

Hide
sergey added a comment - 05/Jun/13 6:10 PM

Seem like org.eclipse.core.net overrides the https.proxy* system settings, it starts after our licensing plug-in, so first few requests are going through the proxy, others are not. Have added the proxy status logging for debugging.

Show
sergey added a comment - 05/Jun/13 6:10 PM Seem like org.eclipse.core.net overrides the https.proxy* system settings, it starts after our licensing plug-in, so first few requests are going through the proxy, others are not. Have added the proxy status logging for debugging.
Hide
komaz added a comment - 14/Jun/13 5:05 PM

Correct, org.eclipse.core.net does not care about proxy settings from system properties and overrides everything with settings from configuration scope (which is obviously empty in case of Q7 Maven Plugin).

A workaround is to set org.eclipse.net.core.enableProxyService to false.

Show
komaz added a comment - 14/Jun/13 5:05 PM Correct, org.eclipse.core.net does not care about proxy settings from system properties and overrides everything with settings from configuration scope (which is obviously empty in case of Q7 Maven Plugin). A workaround is to set org.eclipse.net.core.enableProxyService to false.
Hide
komaz added a comment - 14/Jun/13 5:10 PM

TODO: need to remove this debug logging, it is too verbose

Show
komaz added a comment - 14/Jun/13 5:10 PM TODO: need to remove this debug logging, it is too verbose
Hide
komaz added a comment - 28/Jun/13 7:18 PM

Let us set this java property automatically in Q7 Runner

Show
komaz added a comment - 28/Jun/13 7:18 PM Let us set this java property automatically in Q7 Runner
Hide
komaz added a comment - 23/Jul/13 2:54 PM - edited

Fixed. Now this property is set automatically

Show
komaz added a comment - 23/Jul/13 2:54 PM - edited Fixed. Now this property is set automatically

People

Vote (0)
Watch (0)

Dates

  • Created:
    04/Jun/13 4:33 PM
    Updated:
    23/Jul/13 2:54 PM
    Resolved:
    23/Jul/13 2:54 PM