Page Comparison

...

There could be error conditions (although occurrence is rare), where the RMsis Database becomes out of sync with JIRA database. This functionality is provided to initiate forced resynchronization of all issues in a specific project.

Diagnosis

1. In RMsis logs, search for the following string "noOfIssues:-1". In case of issues, the search will return the following string pattern:
   1. AsyncProcessorImpl.asyncSyncArtifactsInChunks_aroundBody4(67) | Transaction thread complete: projectId:3 noOfIssues:-1
2. If it is found, then the synchronization should be triggered by respective Project Manager / Administrator.

Functionality

1. Login as AdministratorProject Manager / Administartor
2. On RMsis page, goto RMsis Administration Home > Application Project Configuration > Global Configuration
3. Click on Reset Sync as shown below.

Image Removed

Caution and Recommendation

1. The synchronization process can put considerable load on the JIRA and RMsis databases, compromising the user experience with respect to system performance.
2. Depending upon your system performance and number of issues, this process may take many hours.
3. So if you have moderate to large database, it is recommended to run this process over the weekend OR when there are very few users on the system

Availability

Released as Image Added

Hotfix for RMI-3324

The error cases are now handled and the project will be resynchronized, when a user accesses Reverse Traceability tab.

Availability

This functionality is released along with a hotfix for RMI-3324 as RMsis 1.8.2.2-r.268270.