-
Notifications
You must be signed in to change notification settings - Fork 4
Troubleshooting
Best way to start trouble shooting is to run the above examples. In case those work, then environment variables, Java version and Java Web Start proxy settings should not be the problem.
Cause: The command starting the application is wrong
Solution: By adding "2 > error.txt" at the end of the command you get possible errors to error.txt which is located on the directory where tests are executed. Based on the error, you need to fix the command.
Cause: There are spaces in the program that should be started
Solution: This is known issue in RemoteApplications, see issue 36 for more details and workarounds.
Cause: Proxy settings are incorrect with Java Web Start
Solution: Run command "javaws -viewer" and modify the proxy settings.
Cause: _JAVA_OPTIONS environment variable have settings that affect JVM e.g. Quick Test Pro (QTP) related settings.
Solution: Remove the _JAVA_OPTIONS environment variable or set it empty in test data.
Cause: Multiple Java processes are started with one command and RemoteApplications library accesses wrong JVM
Debugging: See that there are no urls in launched.txt after the connection to the application is created and/or monitor the started processes when running the tests e.g. with [https://visualvm.dev.java.net/ visualvm] tool
Solution 1: Change the command to start only one process
Problem: Could not connect to application XXX
Cause: Testing capabilies are not started when the application is started
Debugging: Check is there URL in launched.txt (see file location from [http://robotframework-javatools.googlecode.com/svn/jvmconnector/trunk/doc/RemoteApplications.html library documentation]).
Solution 1: Remove the file and rerun the test cases. If problem persist, see solutions below.
Solution 2: In case you are using Robot agent, see that -javaagent has proper values (see details from [http://robotframework-javatools.googlecode.com/svn/jvmconnector/trunk/doc/RemoteApplications.html library documentation]). Add "2 > error.txt" to end of the command you are using to start your application and you should see message "Picked up JAVA_TOOL_OPTIONS: -javaagent:/path/to/jvmconnector.jar-/path/to/lib/" in the error.txt if everything goes fine. If not, there should be reason for the failure.
Solution 3: In case you are using "Start Application" keyword and application is started, please submit an issue.
Problem: Take Librar(y/ies) Into Use" keyword fails for ClassNotFoundException
Cause: The library is not available on the application's JVM
Solution 1: Check that you are giving correct directory to "Start Application" keyword's lib_dir argument
Solution 2: In case you are starting the application without using Remote Applications, check that you are giving correct path to the Robot Agent (see details from [http://robotframework-javatools.googlecode.com/svn/jvmconnector/trunk/doc/RemoteApplications.html library documentation]).