Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 9 Oct 2013 16:34:43 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12673044.1381336315951.39520.1381336483104@arcas>
In-Reply-To: <JIRA.12673044.1381336315951@arcas>
References: <JIRA.12673044.1381336315951@arcas>
Subject: [jira] [Updated] (AMQCPP-516) Don't fire transport interrupted
 event when no resume is possuble
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQCPP-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish updated AMQCPP-516:
--------------------------------

    Fix Version/s: 3.9.0

> Don't fire transport interrupted event when no resume is possuble
> -----------------------------------------------------------------
>
>                 Key: AMQCPP-516
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-516
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 3.8.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 3.8.2, 3.9.0
>
>
> Don't fire transport interrupted if there will never be a transport resumed such as the case where maxReconnectAttempts is zero.  


--
This message was sent by Atlassian JIRA
(v6.1#6144)