One way to do is prevent the sucked messages from being merged over to the failover node. That makes those messages stuck in the failed node. Unless the failed node restart and have consumers, the message will never get consumed.
On second thought, "ordering in failure condition" is actually a feature not required by JMS spec? JBM has ordering group doing this. But this specific case, which requires "ordering in cluster under failure", is NOT supported by ordering group, which only support non-clustered (or ha-singleton) queues.
So users who ask for this feature should turn to HornetQ.