Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 2 Jul 2013 16:03:20 +0000 (UTC)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12653692.1371643505820.199320.1372781000137@arcas>
In-Reply-To: <JIRA.12653692.1371643505820@arcas>
References: <JIRA.12653692.1371643505820@arcas>
Subject: [jira] [Commented] (AMQ-4590) AMQP: Only one connection from a
 given container is allowed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-4590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697909#comment-13697909 ] 

Hiram Chirino commented on AMQ-4590:
------------------------------------

While not ideal, it's a 'feature' for JMS clients being implemented over AMQP.  I'd defer modifying the current behavior until a AMQP to JMS spec is finalized and way to enforcing the uniqueness of JMS 'client id' is formalized.
                
> AMQP: Only one connection from a given container is allowed
> -----------------------------------------------------------
>
>                 Key: AMQ-4590
>                 URL: https://issues.apache.org/jira/browse/AMQ-4590
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.8.0
>            Reporter: Gordon Sim
>
> This is because the container id in AMQP is mapped onto the JMS clientid. The limitation prevents another broker establishing more than AMQP connection to ActiveMQ (or else it would need to identify itself as a different container for each).

--
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