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

Justin Bertram commented on ARTEMIS-2353:
-----------------------------------------

Couple of things:
* The attached [^brokerLive.txt] and [^brokerBackup.txt] don't appear to be 
configured as a live/backup pair. Can you shed any light on this?
* Are you sending persistent or non-persistent messages from your STOMP client?
* What STOMP client implementation are you using?

> Artemis Live-Backup Node Cluster Message Lost during Fail over [ STOMP]
> -----------------------------------------------------------------------
>
>                 Key: ARTEMIS-2353
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2353
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker, STOMP
>    Affects Versions: 2.6.4
>         Environment: REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
> REDHAT_BUGZILLA_PRODUCT_VERSION=7.5
> REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
> REDHAT_SUPPORT_PRODUCT_VERSION="7.5"
>            Reporter: Gaurav
>            Assignee: Justin Bertram
>            Priority: Major
>         Attachments: brokerBackup.txt, brokerLive.txt
>
>
> We have single instance of Artemis Live server (2.6.4 version) backed up by 
> Backup server.  Please refer attachments for both Live-Backup broker 
> configuration.
> We are using stomp protocol for messaging (port 61613).
> During failover of Live server, backup server is taking control of processing 
> all incoming requests. We are seeing message loss exactly during fail over 
> time just before switching to Backup server. This seems Live instance could 
> not persist few messages around fail over time on Journal file system as got 
> flush out from in memory session. Major issue is that Client is not getting 
> notified through any exception that message could not persist on broker 
> journal.
>  
> We are looking for broker configuration through which client call can be 
> blocked until published message is not persisted on Journal.
> Any pointer on this issue is appreciated!
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to