Search code examples
javaqueuejmslistenertibco

Creative solution to two different JMS queue listeners (Tibco)


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.


Solution

  • Maybe the "exclusive" feature of EMS is what your are looking for...

    By setting this property on the queue, only one listener can be listening at a time.

    Here is a pertinent link : https://docs.tibco.com/pub/enterprise_message_service_central_administration/1.0.1_may_2009/html/tib_ems_users_guide/wwhelp/wwhimpl/common/html/wwhelp.htm#href=EMS.5.028.htm&single=true