Return-Path: 
 <dev-return-14487-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: (qmail 77827 invoked from network); 26 Feb 2009 11:54:23 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 26 Feb 2009 11:54:23 -0000
Received: (qmail 8891 invoked by uid 500); 26 Feb 2009 11:54:23 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 8699 invoked by uid 500); 26 Feb 2009 11:54:22 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 8688 invoked by uid 99); 26 Feb 2009 11:54:22 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2009 03:54:22 -0800
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Feb 2009 11:54:20 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 737F5234C4A7
	for <dev@activemq.apache.org>; Thu, 26 Feb 2009 03:53:59 -0800 (PST)
Message-ID: <386701317.1235649239471.JavaMail.jira@brutus>
Date: Thu, 26 Feb 2009 03:53:59 -0800 (PST)
From: "Daniel Ellis (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQNET-147) Connection fails to close if a
 producer or consumer has not been disposed (only when using the failover
 transport).
In-Reply-To: <1426006510.1235591040068.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


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

Daniel Ellis updated AMQNET-147:
--------------------------------

    Attachment: ConnectionError.patch

This issue may not be solely due to the failover transport, it may just be that the failover transport identifies an underlying issue.

If you run the unit tests using the standard activemq transport, the tests pass, but I have noticed the following line at the end of the trace output:

ERROR: Unknown command: ConnectionError[ Exception=Apache.NMS.ActiveMQ.Commands.BrokerError: id = 0 ConnectionId= ]

The connection error type is not handled, so the ConnectionError.patch file attached handles this command type and writes the actual error message to the trace.  This is the error that is now displayed:

ERROR: Connection error: Cannot remove a consumer from a session that had not been registered: 0cc617f9-0433-4980-bb0a-6b450166e536:1

I suspect that this error is possibly causing the failover transport to continually disconnect and reconnect.  But that is just a hunch and I have not proved that yet.

> Connection fails to close if a producer or consumer has not been disposed (only when using the failover transport).
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQNET-147
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-147
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>    Affects Versions: 1.1
>         Environment: Using failover transport
>            Reporter: Daniel Ellis
>            Assignee: Jim Gomes
>             Fix For: 1.1
>
>         Attachments: ConnectionError.patch, ConnectionsTests.patch
>
>
> When using the failover transport such as:-
> <defaultURI value="activemq:failover:(tcp://activemqhost:61616,tcp://activemqhost:61616)"/>
> A connection will fail to close if you dispose a connection before disposing a consumer or producer that is associated with the connection.  The dispose call never returns because the failover transport is continually reconnecting due to a KeyNotFoundException.  The KeyNotfoundException is thrown because a session no longer exists in the connection state.
> A number of the existing unit tests fail (actually they never return) when using the failover transport.  When in debug, a DebugAssert is displayed for each error that causes the reconnect.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.