Why doesn 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.
Related Questions
- 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’t the JMS API provide end-to-end synchronous message delivery and notification of delivery?
- Why doesn the JMS API provide end-to-end synchronous message delivery and notification of delivery?