Forum Discussion

mgajudo's avatar
mgajudo
New Contributor
15 years ago

Running loadUI Agent on WinXP Pro SP3

Hi There,

I downloaded the latest nightly build for the loadUI Agent (for Windows) this morning, installed it on a Windows XP Pro SP3 machine. This machine has JRE version "1.6.0_20". As far as I can tell the installation looks fine but when I run the agent on this machine I am unable to properly connect to this agent.

Here is the output from the console when I run the agent:


C:\Program Files\eviware\loadUI-Agent-1.0-beta1
Starting OSGi Framework...
ERROR: Error starting file:/C:/Program%20Files/eviware/loadUI-Agent-1.0-beta1/bu
ndle/loadui-runner-base-1.0-beta1.jar (org.osgi.framework.BundleException: Unres
olved constraint in bundle com.eviware.loadui.runner-base [30]: Unable to resolv
e 30.0: missing requirement [30.0] package; (package=com.eviware.loadui.api.agen
t) - [30.0] package; (package=com.eviware.loadui.api.agent))
org.osgi.framework.BundleException: Unresolved constraint in bundle com.eviware.
loadui.runner-base [30]: Unable to resolve 30.0: missing requirement [30.0] pack
age; (package=com.eviware.loadui.api.agent) - [30.0] package; (package=com.eviwa
re.loadui.api.agent)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3421)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1754)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1188)

at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264
)
at java.lang.Thread.run(Unknown Source)
log4j:WARN No such property [maxFileSize] in org.apache.log4j.FileAppender.
log4j:WARN No such property [maxBackupIndex] in org.apache.log4j.FileAppender.
09:43:30,574 WARN [DefaultSoapUICore] Missing folder [C:\Program Files\eviware\
loadUI-Agent-1.0-beta1\.\ext] for external libraries
09:43:30,574 INFO [DefaultSoapUICore] Creating new settings at [C:\Documents an
d Settings\user\soapui-settings.xml]
09:43:31,137 WARN [SoapUIProGroovyScriptEngineFactory] Missing scripts folder [
C:\Program Files\eviware\loadUI-Agent-1.0-beta1\scripts]
09:43:31,480 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/r
esources/xsds/xop.xsd with targetNamespace http://www.w3.org/2004/08/xop/include

09:43:31,527 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/r
esources/xsds/XMLSchema.xsd with targetNamespace http://www.w3.org/2001/XMLSchem
a
09:43:31,527 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/r
esources/xsds/xml.xsd with targetNamespace http://www.w3.org/XML/1998/namespace
09:43:31,527 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/r
esources/xsds/swaref.xsd with targetNamespace http://ws-i.org/profiles/basic/1.1
/xsd
09:43:31,527 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/r
esources/xsds/xmime200505.xsd with targetNamespace http://www.w3.org/2005/05/xml
mime
09:43:31,527 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/r
esources/xsds/xmime200411.xsd with targetNamespace http://www.w3.org/2004/11/xml
mime
09:43:31,527 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/r
esources/xsds/soapEnvelope.xsd with targetNamespace http://schemas.xmlsoap.org/s
oap/envelope/
09:43:31,527 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/r
esources/xsds/soapEncoding.xsd with targetNamespace http://schemas.xmlsoap.org/s
oap/encoding/
09:43:31,527 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/r
esources/xsds/soapEnvelope12.xsd with targetNamespace http://www.w3.org/2003/05/
soap-envelope
09:43:31,543 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/r
esources/xsds/soapEncoding12.xsd with targetNamespace http://www.w3.org/2003/05/
soap-encoding
[INFO] Started bridged http service
-> Framework started!
Registered descriptor: soapUI Runner


When I manually try to add the agent through loadUI I noticed in the agent's console I receive the following until I turn off the connection to the agent from loadUI:

09:47:03,046 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:08,546 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:09,608 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:10,968 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:11,983 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:12,999 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:14,014 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:15,030 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:16,030 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:17,046 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:18,046 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
09:47:19,046 WARN [log] javax.net.ssl.SSLException: Unrecognized SSL message, p
laintext connection?
...


I hope this information helps fix any issues going forward.

Cheers,
-Mark
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi!

    hmm.. are you sure you specified https as the protocol for the runner IP in the loadUI application?

    regards!

    /Ole
    eviware.com
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    There seems to be a problem in the latest build. We renamed some packages and it seems that we missed updating the names in some places. This is why you're getting that BundleException. I'll try to fix it on Monday, but until then I'll attach a replacement bundle which should work. Just download this attached file and place it in the bundle directory of your main loadUI directory, overwriting the existing file. Or, wait until after Monday and the nightly build should work again!

    EDIT: The forum doesn't allow attaching jar files, so you will need to manually rename the file to remove the extra 'doc' extension.

    EDIT 2: This is now fixed in the latest nightly build, so the file has been removed.

    Regards,
    Dain
    eviware.com
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    This should now be fixed in the latest build. Please try uninstalling your current version of the loadUI agent and replacing it with the latest nightly build.

    Regards,
    Dain
    eviware.com