From users-return-49942-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Wed May 2 08:02:21 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id ED8A018065D for ; Wed, 2 May 2018 08:02:20 +0200 (CEST) Received: (qmail 93304 invoked by uid 500); 2 May 2018 06:02:19 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 93283 invoked by uid 99); 2 May 2018 06:02:18 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2018 06:02:18 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 36E68C0354 for ; Wed, 2 May 2018 06:02:18 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.567 X-Spam-Level: **** X-Spam-Status: No, score=4.567 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_ENVFROM_END_DIGIT=0.25, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972, URI_HEX=1.313, URI_TRY_3LD=0.832] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id w3OT86e-Tf2u for ; Wed, 2 May 2018 06:02:16 +0000 (UTC) Received: from n4.nabble.com (n4.nabble.com [162.253.133.72]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 6E2705F5B1 for ; Wed, 2 May 2018 06:02:15 +0000 (UTC) Received: from mben.nabble.com (localhost [127.0.0.1]) by n4.nabble.com (Postfix) with ESMTP id 990E21A8518A1 for ; Tue, 1 May 2018 23:02:05 -0700 (MST) Date: Tue, 1 May 2018 23:02:05 -0700 (MST) From: pragmaticjdev To: users@activemq.apache.org Message-ID: <1525240925590-0.post@n4.nabble.com> In-Reply-To: References: <1523448563003-0.post@n4.nabble.com> <1524146450628-0.post@n4.nabble.com> <1524548906501-0.post@n4.nabble.com> Subject: Re: Using ActiveMQ For Distributed Replicated Cache MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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