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 jmstemplate in spring?
Can I Use XML to transform more than 10 mb of data? Trasnsfom inbetween two module/methods etc. If not how can I do.
What is JMS application ?
What is asynchronous messaging in jms?
What is jms queue?
What is Byte Message ?
What is jms endpoint?
How to handle non-transacted sessions with respect to jms?
What is a connection factory?
What is object message ?
What are jms channels?
How do I use a startup class to initialize and later reference jms objects?