Hamilton Araujo created AMQNET-509:
--------------------------------------
Summary: trackMessages issue NMS
Key: AMQNET-509
URL: https://issues.apache.org/jira/browse/AMQNET-509
Project: ActiveMQ .Net
Issue Type: Bug
Components: NMS
Affects Versions: 1.7.0
Environment: Windows Vista 64-bit, Apache.NMS 1.7.0.3635,
Apache.NMS.ActiveMQ 1.7.0.3660, 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
(v6.3.4#6332)
