TIBCO consumer, WebLogic JMS, reconnecting

Question

We're currently running TIBCO 7.2 processes with WebLogic 7 as the JMS and DB connection factory.
          When using weblogic.jar to access JMS, we have discovered that TIBCO seems to loose connection entirely if a JMS server node dies, even when using distributed queues.
          We have implemented the 'forward-delay' option to process messages from queues without an active consumer, in the event of a physical node failure. When this occurs however, TIBCO will not automatically reconnect.
          Does anyone know of a work-around or whether or not this is resolved with the WL 9 releast of weblogic.jar?
          The issue is that the entry point to TIBCO processes is to listen on a queue. Once the connection is broken, the component stops listening for messages.

Answer 1

Hi Uday,
The best option depends on your use case.
A messaging bridge is usually only appropriate when you want to store-and-forward from a local destination to a remote destination, instead of directly sending to the remote destination. Store-and-forward is helpful when you still want to be able to produce a message even when the remote destination is unavailable.
SAF Agents are a store and forward solution, just like bridges, but are only designed to only work with WebLogic JMS destinations.
For links to WebLogic Messaging white-papers, blog posts, samples, and documentation, click Enterprise Grid Messaging on the [url http://www.oracle.com/technetwork/middleware/weblogic/overview/index.html]Oracle WebLogic Product Page.
Specifically, see the [url http://download.oracle.com/docs/cd/E17904_01/web.1111/e13727/interop.htm#JMSPG553]Integrating Remote JMS Providers FAQ, which should help you choose between WebLogic's various JMS integration options.
Hope this helps,
Tom