DOORS Next Log Delta Monitoring Task (DMT) may stall resulting in processing delays (Affects Log based only)

Content

Delays in DMT processing can result in stale data in Reporting under Lifecycle Query Engine (LQE) and in Linking under Link Index Provider(LDX).

This is a regression introduced in V7.0.3 interim fix022 and V7.1 interim fix007 and later interim fixes.

Refer to Known Issue DT468525 for more details.  

Detecting the issue:

1. Check the Tracked Resource Set page for the DMT Status.
2. Navigate to : https://<JazzServerName>/rm/admin/#action=com.ibm.rdm.fronting.server.web.trs
3. Check how far behind TRS processing is (days/hours/minutes/seconds).
4. 
5. If the DMT is behind and it is not catching up then enable debug logging as per: DMT Debug Logging Setup for the following class: "com.ibm.rdm.fronting.server.services.trs.internal.logbased.TrsDeltaMonitorTask"
6. After 1 hour of the debug logging in place, review the rmTRS.log and if you see the following messages repeating in the log, then you may be impacted by this issue.

7. 2026-05-06T10:32:59,469+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - DMT: no compensations found.
   2026-05-06T10:32:59,472+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - Watermark present
   2026-05-06T10:32:59,477+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - Earliest (adjusted) next baseline for lwm 2026-05-06 13:23:55.37 is Optional[2026-05-06 13:52:25.309]
   2026-05-06T10:32:59,478+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - DMT: waiting for pending change(s) to be committed/aborted at 2026-05-06 13:23:55.37
   2026-05-06T10:32:59,478+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - containerRecovery: begin
   2026-05-06T10:32:59,482+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - containerRecovery: end
   2026-05-06T10:33:01,486+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - DMT: no compensations found.
   2026-05-06T10:33:01,489+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - Watermark present
   ........
   2026-05-06T11:36:57,768+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - DMT: no compensations found.
   2026-05-06T11:36:57,771+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - Watermark present
   2026-05-06T11:36:57,775+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - Earliest (adjusted) next baseline for lwm 2026-05-06 13:23:55.37 is Optional[2026-05-06 13:52:25.309]
   2026-05-06T11:36:57,775+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - DMT: waiting for pending change(s) to be committed/aborted at 2026-05-06 13:23:55.37
   2026-05-06T11:36:57,775+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - containerRecovery: begin
   2026-05-06T11:36:57,778+0200 [][TRS DMT] DEBUG services.trs.internal.logbased.TrsDeltaMonitorTask - containerRecovery: end

8. If you are seeing this behavior, contact IBM support.

Temporary workaround:

• Restarting the RM server can help unblock the DMT and allow it to continue to process.