You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2017/03/07 13:41:38 UTC

[jira] [Closed] (AMQ-6618) ActiveMQ with outbound bridge looses message when party not available

     [ https://issues.apache.org/jira/browse/AMQ-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-6618.
-----------------------------
    Resolution: Not A Problem

> ActiveMQ with outbound bridge looses message when party not available
> ---------------------------------------------------------------------
>
>                 Key: AMQ-6618
>                 URL: https://issues.apache.org/jira/browse/AMQ-6618
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.14.4
>         Environment: Testing before pushing to customer
>            Reporter: Gerben de Geus
>              Labels: newbie
>
> An outbound queue looses message(s) when starting and stopping an instance while the remote broker is not available.
> Start with two brokers and a working outboung bridge from source to destination broker.
> Stop both brokers. Comment-out the bridge definition completely.
> Start source broker, and push some messages on source queue.
> Stop source broker, comment-in the bridge and start ONLY the source broker.
> Stop source broker, comment-out the bridge and start ONLY the source broker.
> Result: source queue is empty.
> Probably the outbound bridge was killed while trying to open the communication channel when stopping the service.
> Is some form of transactional behavior defined in the outbound bridge?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)