| Problem | Description | Solution |
|---|---|---|
| A "transaction rollback" error occurs | In the user interface, a message indicates that
a business rule stopped responding. The input parameters to the business rule might be wrong. Also, the attribute or element that triggered or is referenced from the business rule might be broken or contain unexpected data. |
Reproduce the steps that lead to the error. Obtain the stack trace that is in the log file and send the file to IBM Software Support. |
| A "null pointer exception" error occurs | A null pointer exception is a runtime error. | Reproduce the steps that lead to the error. Obtain the stack trace that is in the log file and send the file to IBM Software Support. |
| A "batch indexing failed” error occurs | A "batch indexing failed" error message is written
to the logs when the search index fails to be updated. This failure usually occurs when data cannot be accessed in a workspace. The index queue might contain references to elements, a workspace, or attributes that do not exist or that contain unexpected data. This error might occur if you add an attribute to a module and delete that attribute before the search index is updated with the new attribute. |
Obtain the stack trace that is in the log file and send the file to IBM Software Support. You might need to provide IBM Software Support with additional information from SQL queries. |
| Information is displayed inconsistently in Rational Focal Point | When you save a filter or load the tree view,
information might be displayed inconsistently. Rational Focal Point uses Java applets and runs JavaScript to display the information in the browser. The inconsistencies might be caused by corrupted caches in the browser and Java. Also, the Java might be corrupted. |
|
| Generated files, such as workspaces and Microsoft Excel files, cannot be downloaded in Rational Focal Point | When this error occurs, a message states that
the files cannot be downloaded from the Rational Focal Point server. This error occurs because cache policies conflict between the files that are generated by Rational Focal Point and the web server or proxy that is used by the browser. |
The default cache control policy for downloading
files is set to public. You can change the cache control policy by running an SQL query. Restriction: In
the SQL query, the CC parameter
value must be supported and defined by w3c protocols. For more information,
see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9
|