Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 6 Dec 2012 05:40:58 +0000 (UTC)
From: "SuoNayi (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <1757753448.67073.1354772458921.JavaMail.jiratomcat@arcas>
In-Reply-To: <43863267.137157.1348797187873.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (AMQ-4085) When InvalidClientIDException the
 failover transport for client should retry to connection the broker
 transparently
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

SuoNayi commented on AMQ-4085:
------------------------------

Timothy, image that I have a durable subscription identified by a unique client id in one application instance.
I want to employ the exclusive subscription feature just like the regular exclusive queue subscription via specifying parameter 'exclusive' to true.
When the current durable subscription goes down the other durable subscription with the same client id in other application instance can take it over.
In one word,how to enable the exclusive subscription feature for durable subscription?

                
> When InvalidClientIDException the failover transport for client should retry to connection the broker transparently
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4085
>                 URL: https://issues.apache.org/jira/browse/AMQ-4085
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: activemq-pool, Broker, JMS client
>    Affects Versions: 5.x
>            Reporter: SuoNayi
>            Priority: Minor
>              Labels: InvalidClientIDException, failover
>             Fix For: NEEDS_REVIEWED
>
>
> With the current solution,when using the connection to create session the InvalidClientIDException will be thrown but the underlying failover transport takes no far actions.
> For creating session successfully, you have to recreate a new connection instance(close the old one),this is not good for the shared connection style such as Spring JMS or activemq-pool.
> We would like the transparent reconnect transport insteand of creating new connection.
> I have commented this at https://issues.apache.org/jira/browse/AMQ-3792.

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