Interested to Buy Any Domain ? << Click Here >> for more details...
Why doesn’t the JMS API provide end-to-end synchronous message delivery and notification of delivery?
- 1 Answers
- 2452 Views
- I also Faced
- E-Mail Answers
Answer / 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 |
What is a topic in messaging?
What is the use of connection factory in jms?
Is jms a message broker?
Explain the process of Configuring Queues in Jms?
What is Point-to-Point Approach?
For sending messages through JMS, what encryption options are there?
What is spring jms?
what is topic and what is queue ?
How may messaging models do JMS provide for and what are they?
Which messaging is generally used in cases where a message is published by a producer and consumed by multiple subscribers?
What is Stream Message ?
Why doesn’t the JMS API provide end-to-end synchronous message delivery and notification of delivery?
Core Java 
