Also, let's establish for sure whether the problem is that the Camel route
is occasionally failing to publish to the topic, or that messages make it
to the topic but are lost before consumption.  Add a log line the prints
the current ID as the very last step in your Camel route; if there are
gaps, your problem is in Camel, and if not then it's in ActiveMQ.
On Mar 1, 2016 9:44 PM, "Tim Bain" <tb...@alumni.duke.edu> wrote:

> You can quickly test that by inspecting the subscription via JMX on the
> broker; it'll have a flag that tells you whether it's durable.  If not,
> submit a bug in JIRA.
> On Mar 1, 2016 8:08 PM, "mtod" <m...@thetods.net> wrote:
>
>> Sorry yes I did read his post.
>>
>> I was already using a durable subscription.
>>
>> C# code.
>>
>>         public SimpleTopicSubscriber(string topicName, string brokerUri,
>> string clientId, string consumerId, string filter, string userID, string
>> password, string message)
>>         {
>>             try
>>             {
>>                 this.topicName = topicName;
>>                 this.connectionFactory = new ConnectionFactory(brokerUri);
>>                 if (!String.IsNullOrEmpty(userID))
>>                 {
>>                     this.connection =
>> this.connectionFactory.CreateConnection(userID, password);
>>                 }
>>                 else
>>                 {
>>                     this.connection =
>> this.connectionFactory.CreateConnection();
>>                 }
>>                 this.connection.ClientId = clientId;
>>                 this.connection.Start();
>>                 this.session = connection.CreateSession();
>>                 ActiveMQTopic topic = new ActiveMQTopic(topicName);
>>
>>                * this.consumer = this.session.CreateDurableConsumer(topic,
>> consumerId, filter, false);*
>>                 this.consumer.Listener += new MessageListener(OnMessage);
>>             }
>>             catch(NMSException ex)
>>             {
>>                 Console.WriteLine(ex);
>>             }
>>         }
>>
>>
>>
>> I did just find an older 2009 post where the NMS C# code did not work. I'm
>> not sure if that has been fixed.
>>
>>
>> http://activemq.2283324.n4.nabble.com/NMS-durable-consumer-not-durable-td2366254.html
>>
>> I'm going to setup the same test using JMeter and see if I can get the
>> same
>> results.
>>
>> Thanks
>>
>> Mike
>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/Help-with-a-Failover-testing-that-shows-missing-messages-tp4707916p4708791.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>

Reply via email to