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

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15899393#comment-15899393 ] 

Christopher L. Shannon commented on AMQ-6618:
---------------------------------------------

Are you using persistent messages? This seems odd to me as persistent messages on a queue shouldn't just disappear off the queue unless they were consumed.  According to your scenario in step 3 and 4 the bridge was never reconnected (even though it was added) because the remote broker was offline so there shouldn't be a consumer to get the messages unless you had a local consumer.  You might want to turn on debug logging and take a look and see what the logs say.  The logs should give some indication of what happened to the messages (if they were consumed and acked, or sent to the DLQ, etc)

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