Known issues and workarounds

Restarting Z Refactoring Assistant containers

You can take the following steps to restart IBM® watsonx Code Assistant™ for Z Refactoring Assistant containers:
  1. Run ./stop.sh to stop the running Z Refactoring Assistant containers.
  2. Run ./start.sh to start Z Refactoring Assistant again.
Note: If you forget the OrientDB password, you need to wipe out all the data and start fresh. In this case, you must run ./stop.sh --all first and then ./start.sh to perform a fresh start.

Getting errors in the Z Refactoring Assistant Web UI after it has been left unused

If you leave the Z Refactoring Assistant unused for a while, the authentication token might get expired and then you will see errors in the UI. To resolve the errors, go to the login page and log in again.

The same errors occur when you open Z Refactoring Assistant in multiple browser tabs at the same time. Because opening multiple browser tabs interferes with the ability of Z Refactoring Assistant to refresh the authentication token. You must open Z Refactoring Assistant only in one browser tab at all times.

Getting a bad gateway error when trying to access Z Refactoring Assistant

If you get a bad gateway error when trying to access Z Refactoring Assistant, check and make sure that the PROTOCOL in config.properties is set correctly. For example, if ADDI is not configured to use https, the value needs to be changed to http.

Operation failures for no apparent reason

If operations fail for no apparent reason and cannot be recovered through the user responses as described in the Messages section, it's possible that the number of database connections has been exhausted. In such cases, try reloading the browser page to trigger a recovery process and then try the operation again.

Timeout error

Due to the limitations of Z Refactoring Assistant, a timeout error might occur when you handle large and complex programs. To fix the timeout error, complete the following steps to extend the default timeout length (360 seconds):
  1. In the config.properties file, add the following entry:
    RA_API_TIMEOUT=<seconds>
    Replace <seconds> with the timeout length that you want to set, for example, 720 seconds.
  2. Restart Z Refactoring Assistant.

Key Conditions view disappears while using Action Menu

The Key Conditions view might be empty after you click a key condition’s Action Menu icon (The image shows the Action Menu icon.) while using Visual Studio Code version 1.88.0 or later. This happens because focus is moved away from the active text editor that is responsible for populating the Key Conditions view.

To fix the problem and prevent focus from shifting to the other editor group, close any open editors or views that are in Editor Groups next to the active text editor that contains your program source.

Secure communication issues

If you have issues with secure communication between Z Refactoring Assistant and other components, such as SSL certificate validation errors especially with self-signed certificates, try placing the certificates directly in the /path/to/certificates directory with the following names. Then, restart Z Refactoring Assistant.
  • ad.crt for the ADDI certificate
  • db.crt for the database certificate
Note: The /path/to/certificates directory refers to the CERTS_LOCATION that is defined in the config.properties file.