Why doesn’t the JMS API provide end-to-end synchronous message delivery and notification of delivery?
Answer Posted / munnu
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.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
How do I start jms server?
Explain about session interface?
What is difference between JMS and Web Services?
Explain Asynchronous Message Consumption in JMS?
What is the best message queue?
Can a jms queue have multiple listeners?
What is jms template?
Does kafka support jms?
What is difference between queue and topic?
What are the components of JMS?
What is the use of jmstemplate in spring?
What is jms connection factory in weblogic?
What is MOM in reference to JMS?
What is the publish-and-subscribe model in jms?
What is a message in software?