A production MTP is experiencing frequent restarts and the nospace column in protocolstats has large numbers. What are possible causes?
Using full logging in a TIM or MTP in production is never recommended.
A nospace condition for an APM CE (CEM)-enabled TIM with full logging may occur, due to one of the following two conditions:
Full logging may be used sparingly (Preferably off-hours to debug a condition). If logging must be kept on, use a trial and error approach to see which TIM Trace options do not cause the restart/RAMDisk nospace condition.