Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 722E2200C64 for ; Fri, 28 Apr 2017 15:28:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 70C0B160BA3; Fri, 28 Apr 2017 13:28:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AFDF6160B8C for ; Fri, 28 Apr 2017 15:28:17 +0200 (CEST) Received: (qmail 73931 invoked by uid 500); 28 Apr 2017 13:28:16 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 73920 invoked by uid 99); 28 Apr 2017 13:28:16 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Apr 2017 13:28:16 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 7E4CBE0005; Fri, 28 Apr 2017 13:28:16 +0000 (UTC) From: jbertram To: dev@activemq.apache.org Reply-To: dev@activemq.apache.org References: In-Reply-To: Subject: [GitHub] activemq-artemis issue #1204: ARTEMIS-1112: don't block live activation if a... Content-Type: text/plain Message-Id: <20170428132816.7E4CBE0005@git1-us-west.apache.org> Date: Fri, 28 Apr 2017 13:28:16 +0000 (UTC) archived-at: Fri, 28 Apr 2017 13:28:18 -0000 Github user jbertram commented on the issue: https://github.com/apache/activemq-artemis/pull/1204 Thinking about this more...I'm now not convinced that any changes to Artemis need to be made to support the functionality you're looking for. I believe you could start Artemis in a new thread if you like from your application, and you can use things like ActiveMQServer.registerActivationFailureListener or ActiveMQServer.isActive to stay informed about the status of the broker. Let me know what you think. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---