Unable to launch testrunner.bat from Jenkins (SoapUI 5.1.2)

Hello,

we are building up a continuous integration/testing system orchestrated by a Jenkins master.
When trying to remotely execute the SoapUI testrunner on a Jenkins slave (Windows 7) we receive the error shown below.
The issue occurs with SoapUI Pro 5.1.1 and 5.1.2, under 5.0.0. it works fine.

Exception in thread "main" java.lang.ExceptionInInitializerError
at com.btr.proxy.search.browser.ie.IEProxySearchStrategy.readSettings(IEProxySearchStrategy.java:57)
at com.btr.proxy.search.browser.ie.IEProxySearchStrategy.getProxySelector(IEProxySearchStrategy.java:42)
at com.btr.proxy.search.desktop.win.WinProxySearchStrategy.getProxySelector(WinProxySearchStrategy.java:37)
at com.btr.proxy.search.desktop.DesktopProxySearchStrategy.getProxySelector(DesktopProxySearchStrategy.java:34)
at com.btr.proxy.search.ProxySearch.getProxySelector(ProxySearch.java:193)
at com.eviware.soapui.LicenseHandling$ProxyBackup.backup(SourceFile:698)
at com.eviware.soapui.LicenseHandling.a(SourceFile:91)
at com.eviware.soapui.SoapUIProTestCaseRunner.init(SourceFile:67)
at com.eviware.soapui.SoapUIProTestCaseRunner.main(SourceFile:62)
Caused by: java.lang.RuntimeException: Error loading dllThe system cannot find the path specified
at com.btr.proxy.search.desktop.win.Win32ProxyUtils.<clinit>(Win32ProxyUtils.java:40)
... 9 more
Caused by: java.io.IOException: The system cannot find the path specified
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(Unknown Source)
at java.io.File.createTempFile(Unknown Source)
at java.io.File.createTempFile(Unknown Source)
at com.btr.proxy.search.desktop.win.DLLManager.extractToTempFile(DLLManager.java:116)
at com.btr.proxy.search.desktop.win.DLLManager.findLibFile(DLLManager.java:53)
at com.btr.proxy.search.desktop.win.Win32ProxyUtils.<clinit>(Win32ProxyUtils.java:36)
... 9 more

There is no problem when executing the testrunner locally on the SoapUI machine.
The Jenkins slave service is logged on as Administrator, the same user for which the Pro license has been installed.

Thanks for your help!

Cheers,

--Peter

11 Replies

SmartBear_Suppo
Alumni
12 years ago
Hello,

We have implemented license check in testrunner, the issue is probably because of this. Can you please make sure that you are running this command on a machine with a valid activated soapui license. If you are go to your Control Panel\All Control Panel Items\Administrative Tools open services, look for the jenkins service right click on it and click on properties. On the Log on tab specify your Windows credential. Let me know if this works for you. Thanks.

Regards,
Temil
cwetansk
Occasional Contributor
12 years ago
Hello Temil,

that's what I tried already (see the last sentence in my initial email). The user that is defined in the service Log On tab is the same user for which the SoapUI license has been installed (i.e. "Administrator").
Now, in the Windows service Log On tab the user always shows up as ".\Administrator" (prefixed with the "location" which is the local machine -> see attachment).
Is SoapUI getting confused by this?

Cheers,

--Peter
SmartBear_Suppo
Alumni
12 years ago
Hi,

Thanks for confirming that user has admin privileges.
With the license check, it is necessary for jenkins server to have SoapUI pro license. So Does this user have .soapui folder in which we have the licenses installed?

Thanks,
Jeshtha
cwetansk
Occasional Contributor
12 years ago
Hello Jeshtha,

do you mean that a license has to be placed also on the Jenkins master (even if there is no SoapUI installed on it)???
(As a side node, our Jenkins master runs on AIX...)

On the Jenkins slave where SoapUI Pro is installed and the testrunner executed there is of course a Pro license installed (soapui.key in ../Users/Administrator/.soapui/).

Cheers,

--Peter
SmartBear_Suppo
Alumni
12 years ago
Hi Peter,

If you are still experiencing this problem can you check what user you are running the remote Jenkins slave with? Are you able to run the Jenkins slave directly and not encounter this error or does this error occur only when you launch the slave from the master?

Regards,
Marcus
SmartBear Support
cwetansk
Occasional Contributor
12 years ago
Hello Marcus,
as explained before, the remote Jenkins slave is a Windows service logged on with the same credentials as the user for which the license was installed.
Can you explain me how to run the slave directly (as it's a service)?
For now I can assure you that executing testrunner.bat from the Windows command line works fine.
Also, with SoapUI Pro 5.0.0 we don't have the problem.

Is there now independent license activation for the GUI and for the testrunner.bat?
I see a new flag -l ("Installs an activated SoapUI Pro license file") for the testrunner.bat script.

Cheers,

--Peter
SmartBear_Suppo
Alumni
12 years ago
Hello,

I don't believe the issue is that it is ran as a service. I think the issue is that it is a Jenkins slave and how you are launching the slave for it to run. How are you launching the slave from AIX to run on Windows?

Regards,
Marcus
SmartBear Support
cwetansk
Occasional Contributor
12 years ago
Hi Marcus,

the Jenkins Master starts the slave agent as Windows service on the slave machine. The agent should then run the testrunner script with the LogOn credentials it is configured for.
For more details you might check here: https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-HavemasterlaunchslaveagentonWindows
or here: http://hudson-ci.org/docs/HudsonArch-Remoting.pdf

Cheers,

--Peter
SmartBear_Suppo
Alumni
12 years ago
Hi,

Please run the Jenkins slave that is on the windows system by itself to execute testrunner.bat and see if you run into the license error. If you are able to successfully do this it will narrow the problem down to Jenkins being ran as a slave agent and how that affects the license check for testrunner.

Regards,
Marcus
SmartBear Support
cwetansk
Occasional Contributor
11 years ago
Hi,

I got news on the issue.
We figured out that SoapUI needs to create a folder hsperfdata_Administrator and a file proxy_vole~.dll in a temporary Windows folder.
By occasion it seems to use the Windows environment variable "TMP" to find the temporary folder, which points to "C:\Users\ADMINI~1\AppData\Local\Temp" (same as the env. variable TEMP).

Now it looks as if TMP gets overwritten (it suddenly becomes "/tmp") by the Jenkins Service Wrapper once it starts, a directory that a priori does not exist on our Windows machines.
SoapUI then fails to place the above-mentioned file/folder.

We know now how to treat the issue, but we are not sure what would be the correct/robust fix:
1. Create the directory "C:\tmp" on all Windows machines
2. Add robustness to SoapUI - I would have expected that SoapUI uses the Windows environment variable TEMP rather than TMP (or check its existence)
3. Find out which process in Jenkins sets TMP to "/tmp" and how it can be controlled (java.io.tmpdir?)

We need to investigate more on point 3, but I would like to have your feedback on the issue.

Regards,

--Peter