Why doesn’t the JMS API provide end-to-end synchronous message delivery and notification of delivery?
-Some messaging systems provide synchronous delivery to destinations as a mechanism for implementing reliable applications. Some systems provide clients with various forms of delivery notification so that the clients can detect dropped or ignored messages. This is not the model defined by the JMS API. JMS API messaging provides guaranteed delivery via the once-and-only-once delivery semantics of PERSISTENT messages. In addition, message consumers can insure reliable processing of messages by using either CLIENT_ACKNOWLEDGE mode or transacted sessions. This achieves reliable delivery with minimum synchronization and is the enterprise messaging model most vendors and developers prefer. The JMS API does not define a schema of systems messages (such as delivery notifications). If an application requires acknowledgment of message receipt, it can define an application-level acknowledgment message.
Related Questions
- Why do I get a javax.naming.NameNotFoundException error when I run the JMS example programs in "A Simple Example of Synchronous Message Receives" in Chapter 33?
- What message distribution policy does the JMS API specify when there are two or more QueueReceivers for the same queue at the same time?
- Why doesn the JMS API provide end-to-end synchronous message delivery and notification of delivery?
