com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.
Java Message Service (JMS) Support
- Former user (Deleted)
Owned by Former user (Deleted)
Java Message Service (JMS) is a widely used API in Java-based Message Oriented Middleware(MOM) applications. It facilitates loosely coupled, reliable, and asynchronous communication between different components of a distributed application.
JMS supports two asynchronous communication models for messaging as follows:
- Point-to-point model - In this model message communication happens from one JMS client to another JMS client through a dedicated queue.
- Publish and subscribe model - In this model message communication happens from one JMS client(publisher) to many JMS clients(subscribers) through a topic.
This section provides information on JMS support in WSO2 ESB along with implementation details of common use cases, a configuration guide as well as a troubleshooting guide. In the JMS Usecases section you will also see use cases for the new messaging features introduced with JMS 2.0.
WSO2 ESB supports the following messaging features introduced with JMS 2.0:
- Shared Topic Subscription
- JMSX Delivery Count
- JMS Message Delivery Delay
- JMS Usecases
- ESB as a JMS Consumer
- ESB as a JMS Producer
- ESB as Both a JMS Producer and Consumer
- JMS Synchronous Invocations : Dual Channel HTTP-to-JMS
- JMS Synchronous Invocations : Quad Channel JMS-to-JMS
- Store and Forward Using JMS Message Stores
- Publish-Subscribe with JMS
- Shared Topic Subscription with WSO2 ESB
- Detecting Repeatedly Redelivered Messages via WSO2 ESB Using the JMSXDeliveryCount Property
- Using WSO2 ESB as a JMS Producer and Specifying a Delivery Delay on Messages
- JMS Samples
- Advanced Topics
- JMS Troubleshooting Guide
- JMS FAQ
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.