Why doesn’t the JMS API provide end-to-end synchronous message delivery and notification of delivery?
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 the use of jms? In which situations we are using jms?
What is the functionality of a message listener in the context of jms?
Can we send e-mail messages using JMS?
What is jms server?
Does JMS specification define transactions?
How do I configure jdbc so that the jms jdbc store recovers automatically?
What is the difference between BytesMessage and StreamMessage?
Name the components of jms.
Why doesn't AQ_ADMINISTRATOR_ROLE or AQ_USER_ROLE always work for AQ applications using Java/JMS API?
What are the various message types supported by JMS?
What is the use of jms?
Is it possible to create both queues and topics to single jms server? if yes then how it works?