You might notice this error from RQM Diagnostics, when RQM users report inconsitensies in using their RQM session.This was reported from a production environment.
RQM Diagnostics shows error "CRJAZ1992E The "com.ibm.rqm.process.deployment.CleanDirtyItemInfoTask" task could not be completed and is now unscheduled.
Error details: "Deferred operation failed"
Where to look for RQM Diagnostics:
Login with the below link with your RQM Server specifics:
The recent changes that happened to the server as pointed to us , was that the Database server was accidentally shutdown the day before and post that ,bringing up the Database server and QM application displays this error from RQM Diagnostics.
Environment Details :
OS: RHEL 7
WAS : 188.8.131.52
Reverse Proxy : Yes with IHS
Database : DB2 10.5.
RQM Server restart seem to resolve the error temporarily, but re-surfaces.
Probable impact seem with the users unable to commit their changes made to an artifact or errors during execution.
The primary recommendation is to shutdown and restart the RQM server components in the correct sequence.
CAUTION: Broadcast a message for all users to log out from their current session.
Shutdown the server in the folloiwng sequence:
Shutdown the IHS server.
Shutdown WAS services.
Then start the server using these:
Start DB2 server
Start the WAS profile
Start the IHS server
Post restart , notice if the error disappears else try to note the TIMESTAMP from RQM Server diagnostics, and look into the following logs for the respective entries
1.ISADAC logs for RQM.
2.IHS logs - httpd.log
3.IHS logs - error.log
Note: If the topology is distributed and servers are located in varied timezone than the RQM Web UI user, you should look at the time where the RQM Server and other components are installed to analyse the logs.
IHS logs are huge in size and cannot be opened when IHS is up and running, hence you can copy the logs from IHS install directory and paste it else where to open in a enhanced text editor (Windos notepad has a limitation to open such huge files).
Monitor the server performance and if still continues to display the error, kindly report the error to IBM Middleware Client Support Team with the relevant log entries from each of above log files.