atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hamilton Araujo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-137) trackMessages issue NMS
Date Tue, 08 Sep 2015 15:05:46 GMT

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

Hamilton Araujo commented on ATLAS-137:
---------------------------------------

Hi,
I'm using Apache.NMS 1.7.0.3635 and Apache.NMS.ActiveMQ 1.7.0.3660.
After creating the connection using the trackMessages=true option in the C# client and starting
a producer to send messages to the ActiveMQ broker and later on stopping the broker and restarting
it after few seconds, the messages don't seem to be cached and sent to the broker after reconnection.
Currently I'm using failover as the following uri:
activemq:failover:(tcp://localhost:61616)?transport.trackMessages=true&transport.maxCacheSize=10000
Does trackMessages work only for transactions?'
BTW, I have seen a forum suggestion to use embedded broker, but sounds like NMS does not support
in-memory broker (no C# ActiveMQ). Is there a way to achieve producer messages persistence
while connection is down and send them out to broker after reconnection?
Thanks,
Hamilton.

> trackMessages issue NMS
> -----------------------
>
>                 Key: ATLAS-137
>                 URL: https://issues.apache.org/jira/browse/ATLAS-137
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Hamilton Araujo
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message