activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQNET-509) trackMessages issue NMS
Date Thu, 10 Sep 2015 17:40:46 GMT


Timothy Bish commented on AMQNET-509:

Your best bet for local persistence is to simulate the embedded broker scenario by running
a local broker on the same machine and network that broker to the remote broker you are targeting.
 The client does no offer the type of embedded persistence you are looking for.  

> trackMessages issue NMS
> -----------------------
>                 Key: AMQNET-509
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.7.0
>         Environment: Windows Vista 64-bit, Apache.NMS, Apache.NMS.ActiveMQ, ActiveMQ 5.11.1 
>            Reporter: Hamilton Araujo
>            Assignee: Jim Gomes
> Hi,
> 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 dropping the connection
and reconnecting 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 (or mock?). Is there a way to achieve producer messages persistence
while connection is down and send them out to broker after reconnection without creating my
own code for it?
> Thanks,
> Hamilton.

This message was sent by Atlassian JIRA

View raw message