Why doesn’t the JMS API provide end-to-end synchronous message delivery and notification of delivery?
- 1 Answers
- 1896 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 Service Provider ?
How jndi is related to jms?
What is the difference between jms and mq?
Explain Synchronous Message Consumption in JMS?
What is MOM in reference to JMS?
How to Configure Open JMS?
Are you aware of any major JMS products available in the market?
Mention the difference between durable and non-durable subscription?
Why is my jms work not part of a user transaction (i.e., Called within a transaction but not rolled back appropriately)? How do I track down transaction problems?
What is the main parts of jms applications?
How does a sender application transport/send a message through jms?
What is the number of messaging models available on jms?
Core Java 
