Hi,
Does anyone know how the MTC and the Router tasks interact with each other?
I´m asking this because our Router stops many times during the day with the message “Awaiting Reactivation”. I am begining to suspect on the MTC.
I read on the R5 forum that the MTC pauses the router to process the messages. Is it confirmed?
Is there a workaround/fix?
Thanks in advance.
Rogerio
Subject: Awaiting Reactivation and Message Tracking
By default MTC stops the router every 15 min. See message tracking collection interval on Configuration document for server.
We had problems with MTC as well. I was unable to fix it (and wasn’t really using the data collected anyway) so I shut it off.
Subject: RE: Awaiting Reactivation and Message Tracking
This is not correct. MTC never stops the router. Prior to 6.04/6.5.2, the router paused/resumed during the ‘once a day’ processing of compacting the mail.box(s) and bumping the message tracking data files. The changes for the SPR TMIZ5FPD6L changed that so that message tracking will not cause this pause/resume. If you are seeing a problem after the ‘once a day’ work and it goes away if message tracking is disabled, you are seeing SPR JBAA5EAR2U which should no longer happen with the changes in TMIZ5FPD6L.
If you are seeing a problem at a regular interval throughout the day, it may be SPR MBEN568SES which is cause by a failure of message tracking to initialize. This causes the router to continuously attempt to initialize message tracking. When starting/stopping message tracking inside the router, the router will pause/resume.
The fundamental issue here is not message tracking. The issue is that a router delivery/transfer thread has hung and the router can not pause/resume.
Subject: RE: Awaiting Reactivation and Message Tracking
Hi Douglas,
Thanks for your reply. This confirms that the router needs to be stopped by the MTC. I need this information in order to suggest the MTC deactivation.
Regards,
Rogerio