© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
1.0 Known problems and workaroundsOn Linux, IBM JRE 1.5(JAVA5.0) uses a new windowing toolkit for AWT applications. As a result, AWT-based applications-under-test (AUT) crash when run on IBM JRE1.5. This causes a TargetGone exception.
Workaround:
- In the command line interface enter the following command:
java -Dawt.toolkit=sun.awt.motif.MToolkit
- Or in Functional Tester select Configure->Enable Environments for Testing and add Dawt.toolkit=sun.awt.motif.MToolkit to the Run Options field in the Java Environments tab.
Note: This problem also occurs with Sun JRE 1.5. But the workaround mentioned will not work with Sun JRE 1.5.
This is because of a defect with IBM JRE 1.5.
Workaround: Use Sun JRE 1.5, IBM JRE 1.4.2 SR6 or IBM JRE 5.0 SR3 to playback on HTML.
When two threads in a process submit X requests simultaneously, the X libraries cannot handle the requests because they are not thread-safe. This causes asynchronous errors with messages like Unexpected asynchronous reply or Event lost to occur. This may also occur when multiple threads are used in RFT scripts.
Workaround: In the <RFT installation directory>/ivory.properties file, set the option rational.test.ft.script.playback.mouse.allow_multiple_threads to "true."
On Linux, due to incompatible encoding formats, Functional Tester may not recognise or read the files that are being imported.
In Functional Tester the default encoding format is set to UTF-8. But UTF-8 cannot handle a few encoding formats like Cp1252.
Workaround: On Linux, set the encoding format of the files to ISO-8859-1.
- Select the imported project or the project to which you are importing the files in the Functional Test Projects pane.
- Click Project > Properties.
- In the Properties window, select Info from the list..
- In the Text file encoding field, click Other.
- Select ISO-8859-1 from the drop-down list.
- Click OK.
Sometimes exceptions might occur when you open the Functional Test perspective. This may happen in the following scenarios:
- Opening the Eclipse IDE by running the <Functional Tester installation directory>\eclipse file directly
- Eclipse IDE is opened for a different product that uses the same Eclipse shell as Functional Tester
Workaround:
- Open the Functional Tester using the launch menu or the command ft_starter.
- Set the Functional Tester environment variable before invoking the Eclipse IDE. For example: source <Functional Tester installation directory>/FunctionalTester/bin/rtsetup
Sometimes, when objects are highlighted from the script explorer, they appear in the background and cannot be seen.
Workaround: Add the following line in the Run options of the Java Environments tab in the Enabler tool:
-Dawt.toolkit=sun.awt.motif.MToolkit
While installing Functional Tester, if you have changed the location for installing the Shared directory, the ft_agent_start script cannot start the RAServer.
Workaround: Edit the ft_agent_start script to change the path of the RAServer available in the installed location of the Shared (SDP70Shared) directory.