We've got a situation where two different application instances intermittently listen at the same queue. 

The logical solution is just to point one of them somewhere else or switch one off. 

I wondered if there was a way to configure the Tibco JMS configuration to force one off, or only send message events to one client? I was looking for an 'out of the box' way of thinking about this issue.