Not really, as there are different causes of infinite loop. Prevention is the best cure, so having a robust design and build review procedures is recommended to maintain quality, and that things like loop counters are used and that dangerous nesting of exception handling is avoided.
From control room, maybe the logs can reveal that the process is repeating the same steps over and over? Or maybe if the queue isn't going down normally?
To me, if there is a process that has fallen into an infinite loop then it needs to be redesigned, rather than looking for ways to detect when an infinite loop is happening.
Â