[
https://issues.apache.org/jira/browse/AMQ-4590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521616#comment-14521616
]
Robbie Gemmell commented on AMQ-4590:
-------------------------------------
What we are currently looking to do for the JMS mapping is use a
'sole-connection-for-container' capability to request that the broker/peer
grant exclusive use of a container-id (which will contain the client-id), or
fail the connection attempt if it cant. If the broker/peer doesn't support the
request, it will then be the clients choice whether to fail or not. This will
let clients request JMS 1.1 like client-id behaviour for those that want
it..while leaving it possible for brokers to support multiple connections with
the same container for those that don't (which e.g might include JMS 2.0
clients)
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
