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
- 2456 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 |
Why do I get java.security.AccessControlException when using JMS MessageListeners from Java stored procedures inside Oracle8i JServer?
What is the functionality of a message listener in the context of jms?
What is the publish-and-subscribe model in jms?
Explain about map message?
What are the different places where you can use the JMS API?
What is jms server?
What are the core JMS-related objects required for each JMS-enabled application?
What Is the JMS API?
What is the use of message queues?
Why doesn’t the JMS API provide end-to-end synchronous message delivery and notification of delivery?
Give an example of using the point-to-point model
Is it possible to create both queues and topics to single jms server? if yes then how it works?
Core Java 
