From user-return-27681-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Oct 23 11:41:08 2019 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 96E01180608 for ; Wed, 23 Oct 2019 13:41:08 +0200 (CEST) Received: (qmail 60189 invoked by uid 500); 23 Oct 2019 11:41:07 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 60179 invoked by uid 99); 23 Oct 2019 11:41:07 -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, 23 Oct 2019 11:41:07 +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 DAFEDC25F3 for ; Wed, 23 Oct 2019 11:41:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.001 X-Spam-Level: * X-Spam-Status: No, score=1.001 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-ec2-va.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id TONflJtnNcpB for ; Wed, 23 Oct 2019 11:41:06 +0000 (UTC) Received-SPF: Pass (helo) identity=helo; client-ip=162.255.23.37; helo=n6.nabble.com; envelope-from=pauld@lemur.org; receiver= Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTP id CFA2DC196D for ; Wed, 23 Oct 2019 11:41:05 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id E2E741214047A for ; Wed, 23 Oct 2019 04:41:04 -0700 (MST) Date: Wed, 23 Oct 2019 04:41:04 -0700 (MST) From: pauld To: user@ignite.apache.org Message-ID: <1571830864927-0.post@n6.nabble.com> Subject: Durable message topic subscriptions? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have a system that uses JMS topics with a durable subscription to process events between different applications, and the durable subscription ensures that the subscriber does not loose messages in the event that the consumer is down for some reason. I like the data grid capabilities and would like to see the feasibility of replacing the JMS component with the Ignite Messaging support, but don't see a way to recover a subscriber after an outage. Is there a process within ignite to support this, or would I really need to stick with the traditional JMS broker for a durable topic subscription. Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/