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
Must I place all my class files in the WEB-INF folder and all JSP's outside?
What is Point-to-Point Approach?
Does kafka support jms?
What is message listener?
What is an object message?
What is JMS API Architecture?
What are all the features of JMS API in J2EE platform?
How to Allowe messages to expire ?
Mention the difference between durable and non-durable subscription?
What is jms mean?
What are the different places where you can use the JMS API?
What is the use of jms? In which situations we are using jms?
How does jms queue work?
What is jms consumer?
What is meant by jms?