Why doesn’t the JMS API provide end-to-end synchronous message delivery and notification of delivery?
- 1 Answers
- 1905 Views
- I also Faced
- E-Mail Answers
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
Can we use jms for sending automated e-mails?
What is the publish-and-subscribe model in jms?
How to create an ejb session in order to start a jms connection?
Do text messages use data?
How does spring jms listener work?
How do the wls jms 6.1 server/destination message maximum and threshold values work?
What is the functionality of a jms queue browser?
What are jms channels?
What is the number of messaging models available on jms?
Which messaging is generally used in cases where a message is published by a producer and consumed by multiple subscribers?
What is jms in websphere?
Can two jms servers share the same persistent store?
Why do we need jms?
How do I use a third-party jdbc driver with jms?
Can we have more than one consumer for a jms queue?
