Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 67F80EEBE for ; Thu, 7 Feb 2013 17:31:13 +0000 (UTC) Received: (qmail 61486 invoked by uid 500); 7 Feb 2013 17:31:13 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 61405 invoked by uid 500); 7 Feb 2013 17:31:13 -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 61380 invoked by uid 99); 7 Feb 2013 17:31:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2013 17:31:13 +0000 Date: Thu, 7 Feb 2013 17:31:13 +0000 (UTC) From: "Timothy Bish (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMQCPP-457) Refactor Transports layer for more control over started / stopped state during initialization MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Timothy Bish created AMQCPP-457: ----------------------------------- Summary: Refactor Transports layer for more control over started / stopped state during initialization Key: AMQCPP-457 URL: https://issues.apache.org/jira/browse/AMQCPP-457 Project: ActiveMQ C++ Client Issue Type: Improvement Components: Transports Affects Versions: 3.5.0 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 3.6.0 Need to revisit the Transports layer and make the whole create / start / stop process more deterministic. The transports should do any connection logic until the filter chain is built and started as a whole, and once stopped no more async exceptions should come out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira