Thanks Tim for your valuable comments. 1.
> so you're using message-driven code rather than managing the connection > yourself. In that case you'd want to do the following to handle the error > (by clearing the cache): > https://stackoverflow.com/questions/40654586/spring-jms-set-errorhandler-for-jmslistener-annotated-method On your suggestion of registering an ErrorHandler, I wanted to confirm my understand - Does the subscriber underneath continuously poll activemq and a failure in doing so gets the ErrorHandler implementation invoked? 2. Tim Bain wrote > @JmsListener is typically used with a > DefaultMessageListenerContainer, which interacts poorly with topics if the > subscription is non-durable Are you suggesting we enable durability? Is there an alternative? I ask because theoretically we don't need durability of the messages. If the subscriber is down when the message is published to the queue, it is perfectly ok as the cache is designed to build as requests are received. We go to the RDBMS store on a cache miss and the subsequent requests then are handled by the cache. Thanks! -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
