If the monitored database is a 10g RAC cluster, there is an Oracle bug that prevents Ignite from collecting blocking/locking information. Ignite gathers this information from the V$SESSION.BLOCKING_SESSION column, and on a 10g RAC cluster, this query will periodically hang. When it hangs, it does so for exactly 60 seconds, and waits on a wait event named "DIAG Idle Event".
Because of this issue, Ignite recognizes a 10g RAC cluster and will automatically turn the blocking/locking feature off. There is no current workaround that we know of.