The Rational Test Automation Server does not currently remove Docker containers after they have exited. The containers will exist in a 'stopped' state but should consume only disk resources (not memory). The Docker command docker ps -a shows both running and stopped containers.

This problem is normally not an issue but if the list grows large it consumes disk resources or might make it difficult to find other stopped containers.

On Rational Test Automation Server system (assuming Linux), to view stopped execution containers, use the following Docker command:

docker ps --filter "status=exited" | grep 'EC_[0-9]' | awk '
{print $1}'

To remove stopped execution containers from the system, use the following Docker command:

docker ps --filter "status=exited" | grep 'EC_[0-9]' | awk '{print $1}
' | xargs docker rm

If there are errors encountered during server shutdown or while uninstalling the server, they can be caused by active asset executions in progress. It is recommended to allow any executions in progress to complete before shutting down or uninstalling the server. If you want to force a shutdown, the following commands can be used to identify and stop active containers:

Show all running and stopped containers that are part of server asset execution:

docker ps -a -f 'name=EC_*'

Remove containers, including running containers:

docker rm -f $(docker ps -q -a -f 'name=EC_*')

Rational Test Automation Server for Windows is provided for evaluation purposes. It is intended for non-production use, for example, trials and demonstrations. It is neither supported nor recommended for production use due to insufficient stability and reliability of Docker for Windows while running Linux images at the time of release.

Rational Test Automation Server is tested on both Windows 10 and Windows Server 2016 Standard Edition and it operates correctly. However, it is suitable and supported for non-production use only.  If native Linux is unavailable, you can run Rational Test Automation Server for production use on a Linux virtual machine on their Windows host, provided that the Linux virtual machine is running a supported version of Linux.

When working in multiple Rational Test Automation Server tabs concurrently, a message “You are already logged in” might sometimes be displayed. This message occurs when your session has expired and you have since logged in again, but then attempt a navigation action in a browser tab other than the one in which you logged in.

This is a known Keycloak issue. For more information, see https://issues.jboss.org/browse/KEYCLOAK-5179. To workaround this problem, close the tab and open a new one.

With 10.0, you might expect a reduction in the number of Virtual Users (VUs) supported by IBM Rational Performance Tester Agent depending upon workload characteristics. This variation is the result of the product shipping with OpenJDK™ 8 with OpenJ9 instead of IBM JRE.

OpenJDK 8 with OpenJ9 JRE exhibits a higher utilization of CPU for the workload. Up to 30% or more decrease in the supported VUs capacity may be expected for CPU-bound workloads. However, for memory-bound workloads, a much smaller, if any reduction in VUs capacity may be expected.

If you need higher performance and have access to IBM JRE 8.0.5.35 or later that contains the latest security fixes, you can switch from OpenJDK 8 with OpenJ9 to IBM JRE. For more information, see http://www.ibm.com/support/docview.wss?uid=ibm10956413.