[chrisplough]

Most OTM clients have a scheduled restart in order to refresh the JVM and avoid and potential memory leaks that could affect performance. Prior to OTM/GC3 v5.0 - some of the higher volume clients were restarting daily in order to keep their instances stable and at peak performance. With v5.0 and especially v5.5 - most clients have been able to move towards longer restart cycles - usually weekly, bi-weekly or monthly. I usually recommend weekly or bi-weekly, whichever fits best into regular maintenance cycles.

One note - after a restart all of the OTM caches are empty and the JVM code optimizations (hotspot or otherwise) are cleared. As a result, OTM may be slow for a few transactions.

Hope this helps!

--Chris