In this tutorial I am going to discuss how JMS API ensures reliable messaging by Creating Durable Subscriptions.
A Publish/Subscribe messaging domain is useless, if subscriber is not active while publisher is publishing a message to destination. If we create a durable subscriber instead of the non-durable subscriber, it is possible to ensure reliable messaging. The non-durable subscriber example can be found in publish/subscribe domain examples Spring JMS and ActiveMQ Integration – publish/subscribe domain, JMS Client using JBoss 7 – Publish/Subscribe Messaging, and Configure JMS Client using GlassFish 3
For more on durable subscriber you can read JMS Concepts – Persistent and Durable