Administration and configuration problems

This topic describes some of the problems you may encounter when installing, administering or configuring Rational® Engineering Lifecycle Manager.

Configuring Rational DOORS as a tracked resource set (TRS) provider

When configuring Rational DOORS® as a TRS provider you will select Tools > Configure TRS. Occasionally this causes error CRCRD7213W: Unable to update the Tracked Resource Set configuration.

To resolve this error, update any requirement and then select to configure TRS again.

Restarting Jazz Team Server does not restart Rhapsody DM

In an environment where Jazz™ Team Server, Rhapsody® DM and Rational Engineering Lifecycle Manager are all installed into a single JTS (using the default Tomcat and Derby on a Windows 2008 server), restarting the Jazz Team Server does not always restart the Rhapsody DM server.

You may encounter this in the following situations:
  • You cannot access the Rhapsody DM site: https://hostname:9444/dm/web
  • The https://hostname:9444/dm/admin site indicates Rhapsody DM has not been registered with a Jazz Team Server.
  • The Lifecycle Query Engine indicates that Rhapsody DM is not a TRS provider: https://hostname:9444/lqe/web/admin/data-sources

Ensure that Rhapsody DM is properly configured by going to the Jazz Team Server > Configuration > Registered Applications page: https://hostname:9444/jts/admin. There should be a Design Management entry.

Confirm that Rhapsody DM has been started by going to the https://hostname:9444/jts/admin site and going to the Application Administration section and searching for Design Management. If the Design Management section says it is undefined or it does not appear at all, restart the Jazz Team Server.

Incorrect Lifecycle Query Engine classloader setting in WebSphere Application Server causes incorrect version of Derby database to be created

The instructions described in the following topic must be followed in order to deploy the Lifecycle Query Engine correctly:Setting up a WebSphere® Application Server for the Lifecycle Query Engine.

If you encounter an error message similar to the following one when attempting to start the lqe_war in WebSphere Application Server, you may have forgotten to complete the step changing the classloader settings. This log can be found in: WAS_install_dir/AppServer/Profiles/yourprofile/logs/Server1/SystemOut.log
Caused by: ERROR XSLAN: Database at C:\Users\IBM_ADMIN\Desktop\WAS_Config\server\conf\lqe\derbyDB has an incompatible format with the current version of the software.  The database was created by or upgraded by version 10.8.
When the default classloader settings are used, WebSphere Application Server creates a Derby database for the Lifecycle Query Engine using the incorrect version of Derby.
If this has occurred you can resolve the situation by completing the following steps:
  1. In the WebSphere Application Server administration console, stop the lqe_war.
  2. Delete the Derby database that LQE created with the incorrect version of Derby. This database is located in the path set in the lqe.config.location variable you set in step 5 of Setting up a WebSphere Application Server for the Lifecycle Query Engine.

    For example, in the default path of C:\Program Files\IBM\JazzTeamServer\server\conf\lqe find the folder called derbyDB and delete the entire folder.

  3. In the WebSphere Application Server administration console, complete steps 18 through 26 as described in Setting up a WebSphere Application Server for the Lifecycle Query Engine. Ensure that you save the master configuration and start the lqe_war.

Logging out results in a WebSphere Application Server error message

If you are running WebSphere Application Server and you log out of Rational Engineering Lifecycle Manager, you may get the error message SESN0008EA: user authenticated as anonymous has attempted to access a session owned by user..."..

Enable the fix on WebSphere Application Server (V8.0.0.3 or later) by adding a custom session manager property. Click Application servers > server1 > Session management > Custom properties and add the InvalidateOnUnauthorizedSessionRequestException = true custom property.

Alternatively, if you close the browser window rather than explicitly logging out, the session eventually times out on its own.

Upgrading Rational Engineering Lifecycle Manager results in TRS license not being available

After upgrading Rational Engineering Lifecycle Manager, the TRS license may not have been added to the License Key Manager. This will result in the LQE indexing failing and displaying an error similar to the following:
Error 403: CRJAZ0977I The com.ibm.team.jazz.foundation.enterprise server license policy does not allow the com.ibm.team.jis.trs.read operation. 
com.ibm.team.jis.lqe.http.error.HttpForbiddenException: Forbidden
If this occurs, manually add the TRS license to the Jazz Team Server License Key Manager.

Upgrading DOORS Next Generation

When you configure or upgrade the Requirements Management (RM) server, problems can occur with OAuth consumer keys that make the server unusable. Buttons in setup wizard might be disabled, or the following error might occur in the server/logs/rdm.log file: CRJZS0033E Invalid consumer key. If this occurs, see the technote Troubleshooting issues with OAuth consumer keys.

Insufficient WebSphere Application Server heap size results in errors

In the topic Setting up WebSphere Application Server for Rational Engineering Lifecycle Manager we recommend that you set the WebSphere Application Server JVM heap size to 4096MB, or to adjust this to adapt to the number of users or amount of data being processed.

If you encounter errors similar to the following, the issue may be resolved by increasing the WebSphere Application Server memory settings.
  • relm.log
     CRCPC1815E An internal error has occurred.Explanation: 
    java.lang.OutOfMemoryError
  • vvc.log
    CRJAZ1451I An exception occurred while executing the task "LogChangeEventAppenderTask", contributed by component "com.ibm.team.repository".  The task will be rescheduled.
    java.lang.OutOfMemoryError
  • lqe.log
    A fatal error occurred during change log processing. Aborting change log processing for https://jts.server.com:9443/application/trs
    java.lang.OutOfMemoryError

Importing large product file results in error

When importing product trees as described in Importing product trees, if you have not set the WebSphere Application Server Web container thread pool max to 200 as described in the prerequisites, you may encounter an error similar to the following in the relm.log file:
ERROR com.ibm.relm.productdefapi - CRCPC2001E An internal error has occurred.
org.apache.http.conn.HttpHostConnectException: Connection to <host> refused

Feedback