Linux issues

© 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 workarounds
   1.1 AWT crash on IBM JRE 1.5 on Linux
   1.2 Playback on HTML does not work with IBM JRE 5.0 SR1 and SR2 releases on Linux
   1.3 In Linux, calling the RationalTestScript API commands from multiple threads causes asynchronous errors
   1.4 Encoding problems while importing files on Linux
   1.5 Exception occurs while opening Functional Test perspective
   1.6 Highlighted objects cannot be seen
   1.7 Unable to start RAServer

1.0 Known problems and workarounds

1.1 AWT crash on IBM JRE 1.5 on Linux

On 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: 

java -Dawt.toolkit=sun.awt.motif.MToolkit

Note: This problem also occurs with Sun JRE 1.5. But the workaround mentioned will not work with Sun JRE 1.5.

1.2 Playback on HTML does not work with IBM JRE 5.0 SR1 and SR2 releases on Linux

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.

1.3 In Linux, calling the RationalTestScript API commands from multiple threads causes asynchronous errors

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."

1.4 Encoding problems while importing files on Linux

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.

  1. Select the imported project or the project to which you are importing the files in the Functional Test Projects pane.
  2. Click Project > Properties.
  3. In the Properties window, select Info from the list..
  4. In the Text file encoding field, click Other.
  5. Select ISO-8859-1 from the drop-down list.
  6. Click OK.

1.5 Exception occurs while opening Functional Test perspective

Sometimes exceptions might occur when you open the Functional Test perspective. This may happen in the following scenarios:

 Workaround:  

1.6 Highlighted objects cannot be seen

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

1.7 Unable to start RAServer

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.