[
https://issues.apache.org/jira/browse/AMQ-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549944#comment-13549944
]
Timothy Bish commented on AMQ-4204:
-----------------------------------
We welcome contributions, if you really want this improvement the fastest way
to get it done would be to come up with a patch that makes the bridge behave
the way you described, along with some unit tests to validate things are
working as anticipated.
> Do not start JMS Bridge if foreign or local connection is failed
> ----------------------------------------------------------------
>
> Key: AMQ-4204
> URL: https://issues.apache.org/jira/browse/AMQ-4204
> Project: ActiveMQ
> Issue Type: Improvement
> Components: activemq-camel
> Affects Versions: 5.6.0
> Reporter: Yana G
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Have 2 JMSConnectors with one JMS Bridge in each.
> Both having the same local JMSQueue and different remote JMSQueues.
> When start connector, one remote connection fails and it's reconnect is
> scheduled.
> However, the corresponding Bridge is started. So, we have the following
> behaviour:
> 1) JMS Message is published in ocal JMSQueue;
> 2) As Queue has 2(!) consumers, it can be processed by any of them;
> 3) If the broken bridge (without foreign connection) is selected, then
> message will be not processed until the connection succeeds.
> We believe that this is wrong behaviour, as JMS messages are not processed,
> even if there is one proper brigde exists on local queue.
> We expect the following behaviour:
> When foreign (or local) connection fails, do not start corresponding bridges.
--
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
