IBM Support

Rational Change 5.2 Known Problems

Product documentation


IBM Rational Change 5.2 Known Problems and Workarounds


Known problems and workarounds new to release 5.2:

Problem and Workaround
Extended text attributes that are DCMed to pre-5.2 releases will be displayed with formatting mark-up in those releases unless a patch is applied. Get the latest release-appropriate patch to display extended text attributes as plain text in older releases.
The default WASCE memory settings are insufficient for Change. The workaround described below should be made prior to installing Change. Restart WASCE after making this change.

Add the following line to WASCE_HOME\bin\setenv.bat before installation Change:
set JAVA_OPTS=-Xmx512m -XX:MaxPermSize=64m
Add the following line to WASCE_HOME/bin/
JAVA_OPTS="-Xmx512m -XX:MaxPermSize=64m"

Further tweaking of the JVM memory settings may be necessary when running multiple web applications, including more than one instance of Change. You may have to experiment with the "-Xmxsize" and "-XX:MaxPermSize=size" flags.
WAS makes of copy of the web.xml file in the Change installation area. Thus, when making changes to web.xml (such as when changing the port number or protocol) on WAS, you must edit
The Perl API
setUpConnection(protocol, host, port)

has been deprecated and should be replaced with

This affects custom Perl scripts and triggers, which need to be updated to continue working. Triggers may use TriggerParser->get_url() to return the server URL. The URL should be of the form http://host:port/context (e.g., http://localhost:8080/change).
Certain resources (such as the dev_clnt process listed by "ccm monitor") are not released when the Change web application is restarted through the application server (WAS or WASCE). If repeated restarts lead to performance degradation, restart the application server, which will release these resources.
A patch is required for earlier versions of central server to work with Change 5.2 in the same central server cluster. Ensure central server releases prior to 5.2 are at least at patch level 5.0 04 or 5.1 06.
Errors may occur when saving ECP_process.xml or other large CR processes on WASCE. To address this, set the maximum POST data size in WASCE:
1. WASCE server Admin console -> Web Server -> TomcatWebConnector -> edit
2. Change the value of the parameter “maxPostSize” from default value to 0 or <0 to disable the post size limit. This requires a restart of the “TomcatWebConnector”.
The help page "Scripts for Managing Listbox Values" has a table of variables that are wrong. The correct variables are listed in a comment in the browserInfo.js file mentioned on that page.
Change does not correctly run in both HTTP and HTTPS protocols simultaneously; it must be run as one or the other.

Note that WAS makes of copy of the web.xml file in the Change installation area. Thus, when making changes to web.xml (such as when changing the port number or protocol) on WAS, you must edit
Taking an attribute that is of type CCM_EXTENDED_TEXT and converting it to any other type will result in the extended text markup being displayed within the transition log. For example, making _COMMENTS webtype CCM_EXTENDED_TEXT, adding notes with markup and then converting _COMMENTS back to CCM_TEXT will result in the transition log not displaying the old comments that were created as extended text correctly.
Customized email notification templates (.tmpl files) used with previous releases of the ECP NotificationTemplates package need to be updated to import plugins from the ChangeSynergy package. For example, replace:
    //%&registerContentPlugin('reportPlugin', $_bt_dict, '')%
    //%&registerContentPlugin('mimePlugin', $_bt_dict, $_bt_dict)%
    //%&registerContentPlugin('ChangeSynergy::reportPlugin', $_bt_dict, '')%
    //%&registerContentPlugin('ChangeSynergy::mimePlugin', $_bt_dict, $_bt_dict)%
When installing Change against WAS or WASCE, the web server port number in the installer incorrectly defaults to port 8600. The user should instead enter the actual port number of the application server.
The package CMMI_MatrixReports should only be used with ECP_process. Additionally, it should be installed after ECP_process, not before. It may have errors with other processes.
When restarting the Rational Change application through WASCE (for instance, after applying a patch), use the stop/start sequence rather than restart. This is necessary because in WASCE the semantics of restart is not the same as stop/start, and certain components will not be reloaded as expected. See for details.
R#38655 The email submission feature (a.k.a. tokenless submission) that was deprecated in release 5.0 is no longer supported. The Perl and web service APIs can be used to implement similar functionality.

Known problems and workarounds carried forward from previous releases:

Problem and Workaround
Rational Change provides configurable date formats that are independent of locale; it does not adapt numeric formats or sorting orders according to the locale. Rational Change does not support right-to-left layouts and scripts (bi-di).
Transition and report links fail after switching between hostname and IP address URLs, as this invalidates all existing cookies used by the system. To address this, users must delete their cookies after this setting is changed to ensure that transitions and reports will work properly.
Session start-up may fail if the Synergy session user does not have the role specified by initial_role in the .ccm.ini file. To resolve this, give the Synergy session user the role specified by initial_role.
The Change installer only allows 7-bit (US ASCII) characters in paths.
Only one user should be logged into the Admin interface at a time or overwritten changes may result.
Be careful when defining the list of modifiable attributes. If you select an attribute that has a dependent attribute, you should also add the dependent attribute to the modifiable list because the dependent attribute's value will automatically change as the user changes the parent value. For example, if Product Version is dependent on Product Name, when the user changes the Product Name, the Product Version is reset automatically. When the user clicks the Save button, which tries to modify both the Product Name and Product Version, the command will fail because Product Version is not defined as a modifiable attribute.
Bulk transition does not work across databases. The bulk transition operation on CRs in different databases (e.g., from a report using CM Build Queries) may either fail with the message "Could not Execute Command; Try Again" or produce incorrect results. This is because bulk transition references the CRs by CVID, and all CVIDs are assumed to be from the same database (the one the user is logged into).
In the rare event that two users modify the same CR simultaneously, changes made by the the first user to click the Save button take precedence. Modification for the second user fails because the form now contains outdated data and must be reloaded. In this event, the changes made on the form of the second user are lost because the browser window is overwritten with the error message.

To restore the changes, do the following:
1. Bring back the modified form by issuing the browser command Alt + back arrow.
2. Log in a second time and show the CR to be modified.
3. Reapply the changes by cutting and pasting from one window to the other.
Invoking Synergy dialogs against objects may not work correctly for certain object types. For example, when using the "DPR - Summary with Tasks and Task Folder" format, an error message will be displayed if you try to invoke a Synergy dialog from the context menu of the task folder. This is because the object operations are not applicable to task folders.
Conflicting task priority values may result between a CR and its associated task. When auto-assigning a task (by checking Create Task during Submit and Assign or during CR assignment), task priority is set to "medium," yet if you change it, the other values are numerical (1-4). This is a historical peculiarity due to a shared attribute name between CRs and tasks.
The search index is invalidated after:
  • DCM initializing Change databases
  • Changing the read security attribute in the CR process (including the first time it is defined)
  • Adding a new attribute to an ACL rule
After DCM initialization, CR updates may cause duplicate entries in the search index. After changing the read security attribute, searching may not produce any results.

Both of these problems are remedied by recreating the search index. This is done by logging into the Admin interface, clicking the Administration button, navigating to the General Administration tab, and then clicking Regenerate Index.
If you reduce the maximum number of sessions on a host that is currently running more than that number, the additional sessions will not be dropped automatically to correctly represent the server settings. To get this effect, adjust the users/session ratio or disable and then re-enable the host.
Simultaneous start-up of Synergy sessions may cause ACcent aborts on Windows servers. To prevent this, in the Admin interface, click the Administration button and navigate to the Server tab. Use -u temp_directory_path for the "Optional start arguments" field (e.g., -u c:\temp).
Bulk transitions and bulk modifications do not span pages in a paged report. When using the bulk operations, all CRs must be on the same page of the report. It is not possible to select CRs across pages in a paged report.
The Change log file, event.log, should not be deleted from the file system manually, because if you do, it will not be re-created unless you restart Change. Instead, clear the log file from the Admin interface or through the API.
When installing a package that consists of a set of XML report definitions, you must use the package type of "CUSTOMIZATION"; otherwise, the report definitions will not be installed. Only report packages—that is, packages that contain actual report templates, not report definitions—should use the package type of "CSREPORT".
Perl triggers using HTTPS on Windows may have noticeably slower performance as compared to using HTTP.
Performing the "Validate Listbox Configuration Data" operation may take several minutes depending on the complexity of the listbox dependency chain and the number of items in the sublistboxes. The message "A script is taking a long time; do you want to abort?" may appear. If so, do not abort the script; rather, let it run to completion.
A trigger that is not written carefully may cause an infinite loop which will crash Change. This happens if a modification trigger modifies the same CR for which the trigger was initially fired, because this in turn fires the trigger again.

There are two workarounds:
  • Ensure that modification triggers don't trigger themselves again by modifying the same CR.
  • Bound the number of simultaneous trigger processes using the configuration entry MAX_TRIGGER_THREADS. This entry tells Change how many trigger threads can be running at one time. The default value, 0, means there is no limit. A setting of 20 will allow only 20 trigger threads to run at once. If a trigger is in an infinite loop the server will detect that all 20 threads are being used and not allow any more to be created. While this will stop the server from crashing, it will also stop any other triggers from firing. An admin user can then manually kill the offending script process to restore the server to a working state without a restart.
The following table gives some general recommendations for configuring Change. For the best results, start with these figures and refine them through experimentation.

Active Users Min/Max Sessions Session Ratio
1-15 2-5 4
15-50 4-10 5
50-100 6-13 8
100-200 8-20 10
200+ 10-? 10-20

Under some circumstances, all sessions in the session pool may be busy and thus unavailable to satisfy a new user request. In particular, running many reports can tie up back-end sessions and prevent other requests from being satisfied. When this happens, the user will see the message "Failed to get a session: Exceeded retry limit," which is usually indicative of a server configuration issue.

To alleviate this problem, try one or more of the following:
  • Increase the minimum number of sessions.
  • Decrease the users/session ratio.
  • Increase the number of retries for a request.

Out of the box, Change has a maximum heap size setting sufficient to support about 200 active users (each making a request every 5-10 minutes) under normal usage patterns. If the web server process exceeds this threshold, performance may degrade. Periodically check the size of this process, and if it exceeds the maximum heap size threshold, change that threshold to a more appropriate number based on experimentation.

Changing the Java maximum heap size for Change on Jetty:

  • Windows
1. Stop Change.
2. Edit CHANGE_HOME\jetty\win32\change.cfg. Search for the Java maximum heap size flag, "-Xmx", and increase the value to a number more suitable to your needs.
3. Remove and reinstall the service:
CHANGE_HOME\jetty\service.bat /remove
CHANGE_HOME\jetty\service.bat /install
4. Start Change.
  • UNIX
1. Stop Change.
2. Edit CHANGE_HOME/cs_app/bin/ Search for the Java maximum heap size flag, "-Xmx", and increase the value to a number more suitable to your needs.
3. Start Change.

For details on setting the Java memory settings for an application server, consult your application server documentation.
When multiple hosts are used by Change, all system clocks must be synchronized. Otherwise, the modify times on CRs can be incorrect, causing the server to falsely alert users that the CR has been modified by someone else. One manifestation of this problem is failure of the bulk transition feature:
"Transition failed... CR <crid> has been modified by another user, please reload your view."
Attachments may fail to be DCM transferred. DCM only transfers objects in static states. Some attachments may be in the non-static 'public' state and thus are not DCM tranferred. Database upgrade attempts to correct this, but may fail for attachments that are missing required attributes.

This must be resolved manually for each affected database.
1. Remove required attributes from attachment objects. Ensure that "Verify Connect Existence on Promote/Check In" is disabled for the 'binary' cvtype. Similarly, ensure the 'binary' cvtype has no other required attributes. Restart your Synergy session. Restart Change if necessary.
2. Transition attachments to the 'readonly' state. Run the following commands as the CM administrator:
ccm query "has_attr('attachment_name') and status='public' and not has_attr('doorsID')"
ccm ci -state readonly -nocomment @
Using the Synergy integration in a heterogenous UNIX enviroment has the requirement that CCM_HOME, as defined in web.xml, must be same on all platforms.
Error messages and their resolutions:
  • Failed to get a session: Exceeded retry limit
    This message usually occurs when the number of requests made to the session pool is more than it can support simultaneously, which may happen during usage spikes. Fortunately, it is usually a transient condition. Try again. However, if this message occurs frequently, the server may need to have its configuration settings re-tuned.
  • The Rational Change server may have been restarted. You must re-login
    When the Change server is restarted, current user sessions are invalidated and all users must log in again. However, the message above is sometimes displayed erroneously. A user who has been timed out by the server and tries to perform an action while the server is running at capacity (i.e., the number of active users equals the maximum number of users) will get the same message. In this situation, the message is incorrect—the problem is that the server is running at capacity and cannot re-activate the user. If the user does try to login again, it will not work, although the error message will be correct.
  • Could not Execute Command; Try Again
    If a Synergy session fails or becomes unresponsive, any command that runs against it will fail. In this scenario, the above message appears. Change will attempt to replace the session when the session pool is resized. A second attempt will usually succeed.
E-Signature limitations:
  • Attributes with a web-type of CCM_E_SIGNATURE are unavailable on submit and copy dialogs.
  • Later versions of Change cannot validate 4.3 SP1 signatures.
  • E-signatures created on a UNIX Change server do not validate on Windows Change server and vice versa.
CR process customization limitations:
1. The following attributes cannot be changed: problem_number, problem_synopsis, transition_log, and modify_user.
2. The COPY state name is reserved for the copy function and cannot be used for other purposes.
3. The name of an attribute cannot be a JavaScript reserved word (e.g., if, for, case, class, super, etc.), a global property/method name on the Window object (e.g., alert, document, location, self, etc.), or any other global object in the browser context (e.g., escape, Math, etc.).
4. The name of an attribute cannot be a Synergy reserved keyword (e.g., purpose).
5. The name of a state or attribute cannot be greater than 32 characters.
6. The following fields should be alphanumeric strings beginning with a letter:
  • Attribute names
  • State names
  • Role names
  • All base template names
  • Admin name
  • Lifecycle image name
Back-end session start-up fails if ui_database_dir is set. The Synergy database path must be visible to all back-end Synergy sessions, and the ui_database_dir parameter must not be specified in the ccm.ini file. If the ui_database_dir parameter is set, back-end Synergy sessions might fail to start properly and you might see a message similar to the following:

Ccm Start Failed
Warning: ACcent execution aborted in 'lscmds:status'
Notify trigger limitations:
  • After you update a Synergy database for use by Change, the behavior of the mail notify trigger will be different.
  • Users of a non-Change database are allowed to configure their mail using either SMTP or MAPI; Change only allows the use of SMTP. Additionally, non-Change database users are allowed to set individual mail servers. With Change, there is only one SMTP mail server per database.
  • A pack file from a Change database will preserve the mail notify trigger configuration from the original database. This might cause problems if the unpacked database is used in an environment where the mail setup is different than the original environment. In this case, you must run the webdb_patch.bat program again on the database.
  • Any custom triggers defined in Change databases should not use graphical interfaces because there will be no user at the Windows display to respond to them.
When object source is downloaded, the character encoding is that which is stored in the database. In particular, no character encoding translation is done.
Several unused methods have been removed from the apiObjectData object in the Perl API:
1. setReadOnly
2. setRequired
3. setInherited
4. setDefault
In addition, the setValue method has been changed to accept time in seconds like its counterpart getter method. This has been done to remove the inconsistency between set and get methods.
The "View Source" functionality of IE 6 sometimes fails to work on pages that are compressed.

There are two workarounds:
1. Use Firefox instead, as it does not suffer from this problem
2. Disable HTTP compression in the web.xml file. This is done by commenting out the following lines:
Saving a report with a chart doesn't necessarily preserve the chart. This is because the chart is now an image (as opposed to an applet). You must save the complete web page (not just the HTML source), including the chart image files, for the report to display properly.
The admin audit log, CHANGE_APP_HOME/logs/audit_log.xml, may become large as it grows indefinitely. Since it is infrequently updated, this is not normally an issue, but if it grows too large it may need to be archived and then cleared. This can be done two ways:

1. Move audit_log.xml directly from the file system to the appropriate back-up location. The drawback with this approach is that audit_log.xml is not a well-formed XML document as it does not have a root node. This will prevent it from loading in XML tools.
2. From the General tab of the Administration dialog, click Download in the Admin Audit Log groupbox. Save the XML file off to the desired back-up location. Then delete audit_log.xml from the file system. This is the recommended methodology.

If missing from the install area, audit_log.xml will be re-created the next time something needs to be logged.
The Perl API CreateUserSecurityData is obsolete and will be removed in a future release.
Central server mode has the following DCM limitations:
  • Tasks should not be DCMed into or out of central CR databases.
  • CRs should not be DCMed into or out of development databases.
The Synergy admin user must be explicitly listed in the database in order to log into Change as that user. By default, this user is implicitly in the database, and thus not listed by ccm users.
The Synergy integration, which allows Synergy dialogs to be launched from Change, has the following constraints in central server mode:
  • On UNIX, CCM_HOME on the client machine must be the same as the CCM_HOME used by the central server.
  • On Windows, the database must be accessible by the local Synergy installation.
Steps to move/rename a central CR database:
1. Open pt.cfg.
2. Find the path specified by [CENTRAL_CR_DATABASE].
3. Do a search and replace on this path, using the new path as the replacement. This should update one of the [CCM_DATABASE] entries, plus the [CENTRAL_CR_DATABASE] and [DEFAULT_DATABASE] entries.
4. Do a search and replace on the database path in pt_listbox.cfg (for database-specific listboxes)
5. Using the Perl API, do a search and replace on the database path in RDS (for preferencess) using the Perl API PreferenceNameSubstitutionForAllUsers.
6. Restart  Change .
The Synergy command to process e-mail submissions, ccm pt_process_submissions, should only be run on the central CR database, not development databases.
As of Change 5.1, Perl scripts must be updated to use the executable "ratlperl" instead of "perl". This change does not affect triggers, which can use either.

Additionally, the modules HTML::Template and Mail::Sender have been removed from Change. Users that were using these modules for sending email will have to update their scripts to use something else or manually download and install these modules. Also, the ChangeSynergy::EmailHelper module has been changed and isn't backwards compatible.
DCS is not supported between Change 4.3 SP1 and subsequent releases if using e-signature attributes.
R#17169, R#39679
Listbox dependencies are defined and values are saved in pt_listbox.cfg. If you change a dependency in the CR process file (XML), pt_listbox.cfg (in the wsconfig directory) will have the old dependency and will cause a configuration error.
To preserve the dependency, define parent and child attributes together in the process package before installing the package and then define the values. If an attribute is already defined for which you want to create a child attribute, you must move pt_listbox.cfg into a package template (thus ensuring there is no pt_listbox.cfg in the wsconfig directory), delete the references to parent attribute from pt_listbox.cfg, create the child attribute, recreate the process package using that package template, reinstall the process package and then define the listbox values.
Defining a child attribute to a parent attribute which has no values defined yet always works.
The Synergy session user consumes a Synergy license. To compensate, licenses generated for Synergy always include one more Synergy license than originally ordered.
IP address vs. hostname URL configuration

Change can be configured to use IP addresses, fully qualified domain names, or relative paths when generating URLs. This feature has been added for situations where using the hostname alone may cause problems with name resolution. For example, if the server name is eagle, the hostname URL would begin with http://eagle:8600/central.

Note: After switching between hostname and IP address URLs, users must delete their Change cookies, otherwise transition and report links will not work.

1. Stop Change.

2. Determine the desired way to generate links in CHANGE_APP_HOME/WEB_INF/wsconfig/pt.cfg: absolute or relative.

# How links should be generated (absolute or relative)
If you chose relative, proceed to step 4.

3. Determine the desired way to show the host.

a) To use the short hostname or IP address, edit the entry below in CHANGE_APP_HOME/WEB_INF/wsconfig/pt.cfg:

# How to refer to the host (hostname or ipaddress)
b) To use a custom hostname format (e.g., to use a fully qualified domain name or a different IP address), make the changes in red to CHANGE_APP_HOME/WEB-INF/web.xml:

<param-value>(hostname override)</param-value>
4. Delete the file CHANGE_APP_HOME/WEB-INF/wsconfig/system/search.lock if it exists.

5. Restart Change.
Some Synergy session data is not re-initialized by re-loading configuration data. The following steps can be used to re-initialize these sessions for a database without restarting Change. From the Server tab:
1. Select target database.
2. Click Disabled radio button.
3. Save settings.
4. Window will be reloaded automatically.
5. Select target database.
6. Click Enabled radio button.
7. Save settings.
All Synergy sessions serving the selected database will be restarted.
Creation of listbox dependencies can only be done from the Lifecycle Editor. New listbox dependencies cannot be created from the listbox manager interface.
User administration issues
  • Only users with a Synergy User Name in RDS can be administered from Change. If a user is in a Synergy database, but not the directory server, he/she will not appear in the Users tab. Such users must be administered from Synergy.
  • You cannot create new privileges from the Users tab. The workaround is to create the new privilege in Synergy by assigning it to a database user, and then reload the Users tab, which makes the new privilege available for assignment in Change.
  • You can only see/change privileges for databases in which the Admin user has the ccm_admin privilege.
  • If the Users tab loads slowly, change the User and Group List Behavior in the General tab to switch to filter mode if the number of users meets a certain threshold.
  • In central server mode, privileges are only shown for users in the central CR database.
A Change Admin user will not be able to complete all administrative functions if he does not have the ccm_admin Synergy privilege in all  Change databases. In particular, process packages cannot be installed and database privileges can only be seen/changed for databases in which the Admin user has the ccm_admin privilege.
In general, you should navigate Change dialog boxes with the buttons and links provided. Avoid the browser's forward and back buttons (and their associated shortcuts, Alt + forward arrow and Alt + back arrow or Backspace, respectively), as script errors may result. However, there are times when using the forward/back commands is convenient; for example, to retrieve the lost content of a form, to undo accidental forward/back navigation, or to recover from a script error.
Any data from an existing TDS server should be migrated to the new RDS server before connecting it to Change. Failure to do this may result in shared preferences/reports not being migrated.

Invoke the Perl script wsconfig/scripts/ to remove the shared and admin preferences, and then re-attempt the migration.

The following info is needed for running the script:
1. Server name
2. Port number
3. Admin login name
4. Admin's password
5. The database path
The webserver automatically informs the browser of the correct character encoding. However, end users can explicitly change the character encoding the browser uses to display the page. Doing so, and subsequently submitting CR changes to the server, may result in data corruption because the characters sent don't match the expected encoding.
Slow CR load times may result when using McAfee Anti-Virus and Internet Explorer together. This is because recent versions of McAfee Anti-Virus products actively scan scripts in Internet Explorer. Possible workarounds include disabling this feature in McAfee or using Firefox.

Document information

More support for: Rational Change
General Information

Software version: 5.0, 5.1, 5.2

Operating system(s): AIX, Linux, Solaris, Windows

Reference #: 7015941

Modified date: 22 March 2013

Translate this page: