[
https://issues.apache.org/jira/browse/AMQ-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526442#comment-13526442
]
Timothy Bish commented on AMQ-4085:
-----------------------------------
Not returning these exceptions to the client would cause the client to violate
the JMS spec. Also not sure that a denial of service style pattern is really
the best way to implement what you are looking for. You could use advisory
messages to know when a new consumer is needed.
> 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
