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
- 2524 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
Is jmstemplate thread safe?
What are the different types of messaging systems?
What is jms producer?
How does spring jms listener work?
Why do we use message queue?
What is jms message broker?
What is jms used for?
Explain Asynchronous Message Consumption in JMS?
Which messaging modes are included in the java messaging service jms )?
Why does jmssession.createtopic or jmssession.createqueue fail to create a destination in wls jms 6.1 (it worked in 5.1)?
What is jms server?
How do the wls jms 6.1 server/destination message maximum and threshold values work?
Can you use a foreign jms provider to drive an mdb transactionally?
Explain JMS and its Component?
How can third-party jdbc driver be used with jms?
