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
What is jms message broker?
What is Point-to-Point Approach?
What is the important part of JMS applications?
How to read message from jms queue in java?
Explain how Application server handles the JMS Connection?
What is Publish/Subscribe approach?
Which messaging is generally used in cases where a message is published by a producer and consumed by multiple subscribers?
Explain about session interface?
Are foreign destinations handled within foreign jms messages?
What are the basic advantages of jms?
Explain JMS and its Component?
What is wire level protocol?
Explain the process of Configuring Queues in Jms?
How the jms is different from rpc?
What is asynchronous messaging in jms?